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

Shawn Wilsher wrote:
> On 3/6/09 11:29 AM, John J Barton wrote:
>> I suppose this all seems trivial from the inside. It's not the version
>> checking that is any issue, it's the toll in human communications. Bug
>> reports, email, news postings all refer to 3.1. These all refer to
>> something that is now gone. Yes another version will come out called
>> 3.5, but '3.1' does not go away.
> Might I suggest that you use codenames (Shiretoko) in the future then?
> Codenames are created for a reason.

That won't work here:
  this.ff3p1 = versionChecker.compare(appInfo.version, "3.1*") >= 0;

Plus it's not practical because users don't say that, they say 3.1.

>> Not changing the Gecko numbers compounds the problem by the way, since
>> .1 will not map to 3.1 means we have to keep track of the mapping rather
>> than just drop numbers.
> This isn't new.  Firefox 2 shipped on Gecko 1.8.1, Firefox 1.5 shipped
> on 1.8.0, etc.  It'll always be in the user agent, so I'm not sure why
> this is such an issue.

Irrespective of history, I'm just reporting to you that this is one of
the things that makes mozilla hard to work with.

>> It's all annoyingly pointless. So as I said airing this and listening to
>> the rants ahead of time would make it easier to take.
> Maybe it comes across as pointless from your perspective as an add-on
> developer, but try putting yourself in the shoes of, say, a user who is
> wondering why 3.0 -> 3.1 contains so many changes.

This part I don't get: why wouldn't users be delighted with a bulging
new 3.1?

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