I just wanted to post a quick note about this to a wider audience as I have been talking about it in Mozilla meetings…
Firefox 3.6.4 (get the release candidate!) has a platform version of 1.9.2.4. The version number 1.9.2.5 is currently being used by Fennec. We’ll be taking fixes above and beyond that version, so the next platform version Firefox will use will be named 1.9.2.6. We will keep the version numbers coherent by naming it Firefox 3.6.6 (essentially skipping over 3.6.5).
I will be moving the blocking flags and status flags as appropriate, so if you see activity in bugs don’t worry. Also, If you have approvals for 1.9.2.5 they are now for 1.9.2.6 (and should still be landed on mozilla-1.9.2 default).
This is nothing more than a name change, everything still refers to the same Firefox release.
Cue a thousand “what happened to 3.6.5?” questions on release day. Maybe add a brief note to the page that comes up after updating?
Yeah, though I believe we skipped 3.6.1 and no one really noticed (http://www.neowin.net/forum/topic/876094-firefox-361362-whats-going-on/). It may be worthwhile to add a note to the release notes, I’ll think about doing that. There is also a possibility of us finding an unexpected issue with 3.6.4 and having to do a quick turn-around update. If that’s the case we’ll call that version 3.6.5 (even though it is based on 1.9.2.4) and there will be no skip. I don’t intend on that happening, but anything can happen when you ship a large change like this to millions of people.
So just to make sure I understand…. If I have a patch with approval1.9.2.5 I should land it on 1.9.2 default branch. If I have a patch with approval1.9.2.6 then I _also_ land it on 1.9.2 default branch?
By the way, I found about this totally by accident today; it might be a good idea to post about this to the .planning newsgroup or something….
Yep. Unless the approval is an explicit approval for the Fennec relbranch from the Fennec team, the proper place to land is Mozilla-1.9.2 default.
I’ll post it to planning as well. Still getting a handle on the proper communication channels