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
 
John J Barton  
View profile  
 More options Mar 6 2009, 1:52 pm
Newsgroups: mozilla.dev.planning
From: John J Barton <johnjbar...@johnjbarton.com>
Date: Fri, 06 Mar 2009 10:52:45 -0800
Local: Fri, Mar 6 2009 1:52 pm
Subject: Re: Firefox 3.1 becoming Firefox 3.5
Print | View thread | Show original | Report this message | Find messages by this author

Mike Shaver wrote:
> As was discussed at the delivery meeting yesterday, we're proposing to

Sorry I missed this notice yesterday.  I don't think this change is
helplful at this late date in the 3.1 work.

> change the version number of Shiretoko from 3.1 to 3.5.  The increase in
> scope represented by TraceMonkey and Private Browsing, plus the sheer
> volume of work that's gone into everything from video and layout to
> places and the plugin service make it a larger increment than we
> believe is reasonable to
> label ".1".  3.5 will help set expectations better about the amount of
> awesome that's packed into Shiretoko, and we expect uptake help from that as
> well.

As a PR move this is hard to understand. If you sit close you think,
"Ok, 3.1 is slipping so they need to make the target bigger." From far way:
2.0.0.8
...
2.0.0.12
3.0.0
...
3.0.7
3.5

So what follows this trend?  (Seems silly on both extremes to me).

> Work is underway to make sure that we can get the version identifiers
> updated in relevant places like AMO, bugzilla, crash-stats and tinderbox
> with minimal disruption.  Those changes will start to roll out this week.

Well out here in extensions land, we've been relying on the upcoming
3.1. In fact we have been getting badgered to prepare for it.  Now its
suddenly gone. Should I really renumber our extension and all our bug
reports? Maybe I better wait to see what really ships?

Anyway I think a bit more build up would help make this surprise less
unpleasant.

jjb


 
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