lifecycle policy
flag
Messages 81 - 90 of 312 - Collapse all
/groups/adfetch?adid=wQCR7A8AAABo9dHSyfrsXQDZupk2xotK
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
81.  Mike Shaver  
View profile  
 More options May 24 2011, 1:20 pm
Newsgroups: mozilla.dev.planning
From: Mike Shaver <mike.sha...@gmail.com>
Date: Tue, 24 May 2011 10:20:03 -0700
Local: Tues, May 24 2011 1:20 pm
Subject: Re: lifecycle policy
That's not what the link says (click and read it carefully!), and I drafted
the policy with beard originally.

It is commonly misunderstood as you have here, though, so something could
have been communicated better for sure.
On May 18, 2011 2:05 PM, "Robert Kaiser" <ka...@kairo.at> wrote:

> Mike Shaver schrieb:
>> On Wed, May 18, 2011 at 1:15 PM, Matt Brubeck<mbrub...@mozilla.com>
wrote:
>>> Long ago during the Firefox 2.0 cycle, Mozilla's policy was that each

major version would be supported for six months after the next major version
was released [1].


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
82.  Robert Kaiser  
View profile  
 More options May 24 2011, 3:57 pm
Newsgroups: mozilla.dev.planning
From: Robert Kaiser <ka...@kairo.at>
Date: Tue, 24 May 2011 21:57:57 +0200
Local: Tues, May 24 2011 3:57 pm
Subject: Re: lifecycle policy
Mike Shaver schrieb:

> That's not what the link says (click and read it carefully!), and I drafted
> the policy with beard originally.

Asa cleared that up already and apparently that was a long-carrying
wide-reaching misunderstanding then. In any case, it doesn't change our
policy for the future, I guess, so let's just keep the episode in mind
and try not to have something on that scale come up again. ;-)

Robert Kaiser

--
Note that any statements of mine - no matter how passionate - are never
meant to be offensive but very often as food for thought or possible
arguments that we as a community should think about. And most of the
time, I even appreciate irony and fun! :)


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
83.  Kohei Yoshino  
View profile  
 More options May 24 2011, 9:37 pm
Newsgroups: mozilla.dev.planning
From: Kohei Yoshino <yosh...@mozilla-japan.org>
Date: Wed, 25 May 2011 10:37:52 +0900
Local: Tues, May 24 2011 9:37 pm
Subject: Re: lifecycle policy
I thought Fx4 had the same lifecycle policy as before.
If you change the cycle, you should discuss and announce that *before*
the release, or enterprise users get confused :-(

--
Kohei Yoshino
Marketing & WebDev, Mozilla Japan
http://mozilla.jp/


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
84.  Mike Shaver  
View profile  
 More options May 24 2011, 9:44 pm
Newsgroups: mozilla.dev.planning
From: Mike Shaver <mike.sha...@gmail.com>
Date: Tue, 24 May 2011 18:44:15 -0700
Local: Tues, May 24 2011 9:44 pm
Subject: Re: lifecycle policy
On Tue, May 24, 2011 at 6:37 PM, Kohei Yoshino

<yosh...@mozilla-japan.org> wrote:
> I thought Fx4 had the same lifecycle policy as before.
> If you change the cycle, you should discuss and announce that *before*
> the release, or enterprise users get confused :-(

We discussed the update model for after FF4 quite extensively, I think.

Mike


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
85.  Kohei Yoshino  
View profile  
 More options May 24 2011, 10:00 pm
Newsgroups: mozilla.dev.planning
From: Kohei Yoshino <yosh...@mozilla-japan.org>
Date: Wed, 25 May 2011 11:00:03 +0900
Local: Tues, May 24 2011 10:00 pm
Subject: Re: lifecycle policy
On 11/05/25 10:44, Mike Shaver wrote:

> On Tue, May 24, 2011 at 6:37 PM, Kohei Yoshino
> <yosh...@mozilla-japan.org> wrote:
>> I thought Fx4 had the same lifecycle policy as before.
>> If you change the cycle, you should discuss and announce that *before*
>> the release, or enterprise users get confused :-(

> We discussed the update model for after FF4 quite extensively, I think.

I thought this was the decision for Fx4:

http://mozilla.github.com/process-releases/draft/development_overview/


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
86.  Alexander Limi  
View profile  
 More options May 25 2011, 11:34 am
Newsgroups: mozilla.dev.planning
From: Alexander Limi <l...@mozilla.com>
Date: Wed, 25 May 2011 08:34:02 -0700
Local: Wed, May 25 2011 11:34 am
Subject: Re: lifecycle policy

On Wed, May 25, 2011 at 12:55 AM, Henri Sivonen <hsivo...@iki.fi> wrote:
> On Tue, 2011-05-24 at 07:58 -0700, Christian Legnitto wrote:
> > Indeed. Users will also have an option to opt out before applying if some
> of their add-ons are known to be incompatible with the new version (it
> checks and hollers if compat issues ate found)

> Ouch. That basically gives third party developers the power to keep
> users from getting Firefox security fixes.

This is my biggest worry as well. I'd rather disable broken add-ons
temporarily until the author has updated them, especially now that we have
started doing automated version compatibility bumps, so the add-ons on AMO
are mostly handled.

Third-party hosted add-ons (like Skype, antivirus, etc) will have to move
faster under this new model, but they will have to anyway. They shouldn't be
able to stop people from having the latest security fixes, IMO. I'm willing
to go with some pain and aggressively protect our users on this to
straighten out our current (somewhat broken) add-ons story. But I'm also
sympathetic to the other sides in this discussion, it's not an easy choice
to make.

--
Alexander Limi · Firefox UX Team · @limi <http://twitter.com/limi> ·
limi.net


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
87.  Kohei Yoshino  
View profile  
 More options May 25 2011, 9:25 pm
Newsgroups: mozilla.dev.planning
From: Kohei Yoshino <yosh...@mozilla-japan.org>
Date: Thu, 26 May 2011 10:25:28 +0900
Local: Wed, May 25 2011 9:25 pm
Subject: Re: lifecycle policy
On 11/05/25 11:00, Kohei Yoshino wrote:

> On 11/05/25 10:44, Mike Shaver wrote:
>> On Tue, May 24, 2011 at 6:37 PM, Kohei Yoshino
>> <yosh...@mozilla-japan.org> wrote:
>>> I thought Fx4 had the same lifecycle policy as before.
>>> If you change the cycle, you should discuss and announce that *before*
>>> the release, or enterprise users get confused :-(

>> We discussed the update model for after FF4 quite extensively, I think.

> I thought this was the decision for Fx4:

> http://mozilla.github.com/process-releases/draft/development_overview/
>> We'll be using existing branch maintenance processes for
>> Firefox 4.0.x and Firefox 3.6.x security and stability updates.

We're preparing the Rapid Release & Lifecycle FAQ for the upcoming Fx5 beta release in our Japanese locale.
Can anyone answer my question... when and why this policy has been changed?
Does this mean Fx4 will be maintained until this December (6 months after the Fx5 release), right?
We've never heard Fx5 = Fx4 EOL; that's a shocking news.

--
Kohei Yoshino
Marketing & WebDev, Mozilla Japan
http://mozilla.jp/


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
88.  Christian Legnitto  
View profile  
 More options May 25 2011, 9:36 pm
Newsgroups: mozilla.dev.planning
From: Christian Legnitto <clegni...@mozilla.com>
Date: Wed, 25 May 2011 18:36:04 -0700
Local: Wed, May 25 2011 9:36 pm
Subject: Re: lifecycle policy

On May 25, 2011, at 6:25 PM, Kohei Yoshino wrote:

The branch maintenance processes are talking about approving fixes, assorted update channels, bug triage, etc....NOT the support level.

Firefox 5 will be the security update for Firefox 4 and delivered as a minor update.

Thanks,
Christian


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
89.  Mike Connor  
View profile  
 More options May 25 2011, 9:53 pm
Newsgroups: mozilla.dev.planning
From: Mike Connor <mcon...@mozilla.com>
Date: Wed, 25 May 2011 21:53:40 -0400
Local: Wed, May 25 2011 9:53 pm
Subject: Re: lifecycle policy

On 2011-05-25, at 9:25 PM, Kohei Yoshino wrote:

Hi Kohei,

Just to try to clarify, Fx5 does not automatically mean Fx4 is EOL.  As stated, the Fx4 release will follow the old process.  However, it's a common misconception that the policy promised a full six months of support past the next release.  The actual statement in the previous release roadmap reads as follows [1]:

> Adoption of a consumer focused support lifecycle where only the current plus the last major release at any given time would be supported with security and stability updates for up to six months following general availability of the current release.

The key (and deliberately chosen) wording there is "up to six months" as opposed to "at least six months" meaning we may decide to end support sooner.  I do not believe the branch team has made any explicit decisions at this time, but we should avoid making any promises about Firefox 4's EOL date in any official statement at this time.

-- Mike

[1] https://wiki.mozilla.org/ReleaseRoadmap?oldid=168833


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
90.  Mike Connor  
View profile  
 More options May 25 2011, 9:56 pm
Newsgroups: mozilla.dev.planning
From: Mike Connor <mcon...@mozilla.com>
Date: Wed, 25 May 2011 21:56:00 -0400
Subject: Re: lifecycle policy
Ah, please disregard this, I misunderstood.  Christian is responsible for making that call, and he's been clear here!

On 2011-05-25, at 9:53 PM, Mike Connor wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google