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
Message from discussion What's next after Firefox 3 and Gecko 1.9?
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
 
schrep  
View profile  
 More options May 19 2008, 5:38 pm
Newsgroups: mozilla.dev.planning
From: schrep <sch...@mozilla.com>
Date: Mon, 19 May 2008 17:38:13 -0400
Local: Mon, May 19 2008 5:38 pm
Subject: What's next after Firefox 3 and Gecko 1.9?
There have been several discussions of 1.9.1/Moz2 and future product
releases here
(http://groups.google.com/group/mozilla.dev.planning/browse_frm/thread...,
http://groups.google.com/group/mozilla.dev.planning/browse_frm/thread...)
and it has been discussed many times in the Mozilla 2 meetings. Not
everyone could make those meetings but more importantly not everyone was
aware we would be discussing 1.9.1/moz2 there.

In order to drive us closer to conclusion I wanted to consolidate my
understanding of the current plan in *early* draft form below.  I
propose we iterate on this here and take a final form to the
wiki's/blogs for wider distribution.

So please edit, add questions, to the draft below...

Best,

Schrep

*** DRAFT PLAN ****
*******************

Product Releases
----------------

Firefox 2.0.0.x and 3.0.x:

We'll continue the maintenance schedule we set with Firefox 1.5 - namely
doing scheduled maintenance releases of Firefox 3.0.x and Firefox
2.0.0.x every 6-8 weeks.  These releases will focus on security and
stability improvements and cannot add new features, change UX, or break
extensions unless it is required for security purposes or is otherwise
critical.   Since Firefox 3.1 is coming out so quickly after 3.0 I
expect the size of these maintenance releases to be smaller than they
have been for the 2.0.0.x series.  Support releases for Firefox 2.0.0.x
will terminate at the latest approximately 6 months after the shipment
of Firefox 3.    This coincides with the approximate ship date of
Firefox 3.1.

Firefox 3.1:

There were a number of features that we held back from Firefox 3 because
they weren't quite ready - but they were nearly complete.    These
include things like XHR, native JSON DOM bindings, ongoing performance
tuning,  awesomebar++, better system integration, etc.  This along with
the overall quality of Gecko 1.9 as a basis for mobile and the desire to
get new platform features out to web developers sooner has lead to us
want to do a second release of Firefox this year.   This release would
be date-driven and targeted at the end of 2008.   Any features not ready
in time will move to the next major release.  This is currently planned
to be based on Gecko 1.9.1 - but if there are solid technical reasons
for breaking frozen APIs we will bump the version number to Mozilla2.

Firefox Mobile:

There are already devices shipping with early versions of Gecko 1.9 at
the core.  More are coming soon and we'll be releasing milestones of
full branded versions of Firefox (with XUL and the Firefox team taking a
lead in the user experience) later this year.  This lines up well with
Firefox 3.1 and a synchronized release schedule will make everything run
more smoothly.

Firefox 4:

Firefox 4 will incorporate some of the more aggressive platform
improvements in Mozilla2.   It is far too early to set a shipping date
but an initial target would be sometime in late 2009.  Mozilla2 work has
been underway for > 8 months

Platform Releases
-----------------

Gecko 1.9.0.x:

Release date: By end of June 2008
Status: Stable
Accepted Changes: Security, stability, performance, minor enhancements
that do not change *any* exposed APIs.   All changes must pass all
regression tests and not regress performance.
Development Tree: CVS Trunk
Bugzilla Flags: blocking1.9.0.x
Planning Center:

Gecko 1.9.1:

Release date: Beta stable summer 2008, production stable end of 2008
Status: In development
Accepted Changes: Anything that doesn't break frozen API's.   Passing
unit tests and proof of no negative impact on perf from Talos required
before check-in
Development Tree: Hg mozilla-central - will move to a branch before end
of summer 2008
Bugzilla Flags: blocking1.9.1
Planning Center:

Mozilla2:

Release date: Beta stable mid 2009
Status: In development
Accepted Changes: Anything that doesn't regress functionality or performance
Development Tree: Hg mozilla-central
Bugzilla Flags: ?
Planning Center: http://wiki.mozilla.org/Mozilla_2

Q&A
------

Q: I'm running a project based on Gecko and am confused as to weather to
ship on 1.9.0.x, 1.9.1, or Mozilla2?

A: If you are shipping before Nov/Dec 2008 we recommend you ship on
Gecko 1.9.0.x since it is the stable release.  If your product is
shipping after Dec 2008 we'd recommend you use Gecko 1.9.1.x since it
will be stable by then.   If you are shipping later you may want to
consider Mozilla2

Q: Will Firefox 3.1 ship on 1.9.1 or Mozilla2?

A: We will start with 1.9.1 but if there is a compelling technical
reason to break frozen APIs the drivers and module owners may decide to
do so.  If we break frozen APIs we will call it Gecko 2.0 and give fair
notice.

Q: .... please add common questions here..


 
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.