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
 
Gordon P. Hemsley  
View profile  
 More options Mar 7 2009, 10:34 pm
Newsgroups: mozilla.dev.planning
From: "Gordon P. Hemsley" <gphems...@gmail.com>
Date: Sat, 7 Mar 2009 19:34:19 -0800 (PST)
Local: Sat, Mar 7 2009 10:34 pm
Subject: Re: Firefox 3.1 becoming Firefox 3.5
Print | View thread | Show original | Report this message | Find messages by this author
On Mar 6, 2:59 pm, John J Barton <johnjbar...@johnjbarton.com> wrote:

> >> 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

I agree. Since version 1.0, the version numbers have gone 1.0->1.5-
>2.0->3.0->3.5. Both x.5 releases were originally developed as x.1,

but were deemed "bigger in scope" than originally planned. However, as
far as I can tell, the only strictly user-facing improvements in
Firefox 3.1/3.5 are Private Browsing and better tab drag-and-drop. (I
may have missed something, but it's hard to tell, because it's not
documented all in one place.) All of the other (many) improvements
have been in the backend, where they would need to be implemented by a
specific web developer or extension author in order to be useful. So,
as far as I can tell, the user will not see this next release as a
"bulging". There is no real major change that will disrupt user
experience, as there was with the AwesomeBar.

As I said, most of the new features have been implemented in the
backend. As far as I know, that means they were implemented in Gecko,
not specifically Firefox. Yet Gecko's version number is not changing.
This doesn't make much sense to me. Perhaps I'm mistaken?

And I would see Gecko and Firefox versions finally synching as a good
thing. I have expressed from the beginning my support for the fact
that [Gecko 1.9].x == [Firefox 3].x. Why would effort be made to
specifically go back away from that?

I just don't get it, and I would like to express a strong -1 for
upping the version number to 3.5.


 
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