NetRyder
Tech Junkie
- Joined
- 19 Apr 2002
- Messages
- 13,256
Firefox 1.0 "Preview Release" on the horizon...
Ben Goodger said:July 25, 2004
Firefox 1.0 Preview Release
Most of the major work for what will now be called "Firefox 1.0 Preview Release" has been completed, and we're driving a shortening bug list towards zero. We're hoping to have a release in the second or third week of August.
Internally (as in, as far as the Extension and Update systems are concerned) the release will be known as "0.10" and it should be noted that this is not 1.0 - this is what had been called (by the roadmap) "Firefox 1.0 Beta" and recently in the bug system "RC1".
On choosing the name we sought something that did not undermine the fact that we've never labeled any of our previous releases "alphas" or "betas" and despite their pre-release status have gained noticable usage statistics. We felt that releasing a "1.0 beta" may scare people away, so looked for something gentler. We paused on "Release Candidate" but it was correctly pointed out to us that doing release candidates when we know full well that all the content of RTM is not there is somewhat bogus. So we settled on that tride and true moniker, "Preview Release".
To Extension Authors
In the next week or so I will increase app.extensions.version to 0.10. This will end compatibility for all installed extensions with a maxVersion set to 0.9! If existing versions of you extensions are still compatible with the branch since 0.9, please contact update.mozilla.org and get the maxVersion setting in the database increased to 0.10! Code is landing in Firefox at the moment (see previous post) that mean that you do not need to create a new XPI if all you're changing is the maxVersion value in the install manifest! For Firefox 0.9/0.9.1/0.9.2 users this means that when they upgrade to 1.0PR the browser will connect to update.mozilla.org and any custom RDF update files and attempt to version-patch before falling back on looking for new XPIs. 1.0PR users will also be able to install incompatible extensions if a remote version patch is specified that designates compatibility with the new release.
Extension and Theme Authors should start preparing for these changes NOW