Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
mozilla.dev.planning
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion Firefox 3.1 becoming Firefox 3.5
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
 
Dao  
View profile  
 More options Mar 7 2009, 8:26 am
Newsgroups: mozilla.dev.planning
From: Dao <d...@design-noir.de>
Date: Sat, 07 Mar 2009 14:26:19 +0100
Local: Sat, Mar 7 2009 8:26 am
Subject: Re: Firefox 3.1 becoming Firefox 3.5
Print | View thread | Show original | Report this message | Find messages by this author
On 07.03.2009 08:05, eternalsword wrote:

> [...]  second number
> is the development phase toward fixing bugs on the current branch, or
> backporting trunk additions that don't break the API, with even
> numbers being stable releases and odd numbers being development; [...]
> I'm not familiar with the API changes, etc, but I would
> hazard a guess that using this method, there would be 3.0.x security
> releases as there are currently, 3.1 development releases as there are
> currently, and upcoming release would be 3.2, followed by 3.2.x
> security releases and 3.3 development branch.

> I think extension developers would find this numbering scheme more
> beneficial.  Then they wouldn't have to worry as much about their
> extensions breaking just because of maxVersion, since API breaks would
> typically occur at the first number.  That way, maxVersion 3.* would
> cover until the next milestone.

Extensions use all sorts of private interfaces and stuff that doesn't
even deserve the name "interface". Basically, we couldn't touch the
front-end with a secondary number change. 3.1 wouldn't have been
possible that way.

 
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
©2012 Google