I'm extremely late in this (and other) emails, but wanted to give those who haven't been attending various meetings an update on our timelines for Firefox 3.6 Alpha 1 and the upcoming mozilla-1.9.2 branch:
Wednesday, July 30th - deadline/freeze for Firefox 3.6 Alpha 1 Friday, July 31st - release of Firefox 3.6 Alpha 1 Friday, August 7th - branch for mozilla-1.9.1
We're currently marking bugs aimed at Firefox 3.6 Alpha 1 as "blocking-1.9.2+" with the priority field marked as P1:
> I'm extremely late in this (and other) emails, but wanted to give those > who haven't been attending various meetings an update on our timelines > for Firefox 3.6 Alpha 1 and the upcoming mozilla-1.9.2 branch:
> Wednesday, July 30th - deadline/freeze for Firefox 3.6 Alpha 1 > Friday, July 31st - release of Firefox 3.6 Alpha 1 > Friday, August 7th - branch for mozilla-1.9.1
> We're currently marking bugs aimed at Firefox 3.6 Alpha 1 as > "blocking-1.9.2+" with the priority field marked as P1:
Axel Hecht wrote: > On 24.07.09 05:14, Mike Beltzner wrote: >> Hi all,
>> I'm extremely late in this (and other) emails, but wanted to give those >> who haven't been attending various meetings an update on our timelines >> for Firefox 3.6 Alpha 1 and the upcoming mozilla-1.9.2 branch:
>> Wednesday, July 30th - deadline/freeze for Firefox 3.6 Alpha 1 >> Friday, July 31st - release of Firefox 3.6 Alpha 1 >> Friday, August 7th - branch for mozilla-1.9.1
>> We're currently marking bugs aimed at Firefox 3.6 Alpha 1 as >> "blocking-1.9.2+" with the priority field marked as P1:
>> Discussion for this release is taking place in #namaroka
> One question, one clarification:
> Do we have the buildmaster resources for another full-l10n branch?
Yes, we believe we do have enough resources for this.
For RelEng: * This new l10n branch will generate extra load producing new l10n nightlies for 192 in addition to the work for m-c, 191. * This will also generate a repack on checkin for another branch, so some incremental extra work. ...both of which we'll watch and see. If needed, we will spin up extra hardware.
For l10n: * This will mean tracking l10n changes across m-c, and 192 branches. As well, maintaining shipped locales changesets in one extra branch.
I think thats it. Did I miss anything?
> And I'm running on the assumption 3.6a1 isn't going to be a localized > release, is that right? > Axel
> Axel Hecht wrote: >> On 24.07.09 05:14, Mike Beltzner wrote: >>> Hi all,
>>> I'm extremely late in this (and other) emails, but wanted to give those >>> who haven't been attending various meetings an update on our timelines >>> for Firefox 3.6 Alpha 1 and the upcoming mozilla-1.9.2 branch:
>>> Wednesday, July 30th - deadline/freeze for Firefox 3.6 Alpha 1 >>> Friday, July 31st - release of Firefox 3.6 Alpha 1 >>> Friday, August 7th - branch for mozilla-1.9.1
>>> We're currently marking bugs aimed at Firefox 3.6 Alpha 1 as >>> "blocking-1.9.2+" with the priority field marked as P1:
>>> Discussion for this release is taking place in #namaroka
>> One question, one clarification:
>> Do we have the buildmaster resources for another full-l10n branch? > Yes, we believe we do have enough resources for this.
> For RelEng: > * This new l10n branch will generate extra load producing new l10n > nightlies for 192 in addition to the work for m-c, 191. > * This will also generate a repack on checkin for another branch, so > some incremental extra work. > ...both of which we'll watch and see. If needed, we will spin up extra > hardware.
I'm in particular concerned about the perf of the master. We still have an open bug to get l10n builds back to previous responsiveness, see bug 498654.
> For l10n: > * This will mean tracking l10n changes across m-c, and 192 branches. As > well, maintaining shipped locales changesets in one extra branch.
> I think thats it. Did I miss anything?
>> And I'm running on the assumption 3.6a1 isn't going to be a localized >> release, is that right? >> Axel > Correct FF3.6alpha1 will not be localized.
On Thursday 2009-07-23 20:14 -0700, Mike Beltzner wrote [corrected]:
> Friday, July 31st - release of Firefox 3.6 Alpha 1 > Friday, August 7th - branch for mozilla-1.9.2
What are we expecting to accomplish between those two Fridays?
My understanding from last week's Platform meeting was that part of the rationale for separating the alpha release and the branch point by 1 week was to have time to land patches based on feedback from the alpha before we branch. However, I didn't find that argument compelling, since it seems like any patches that fix problems that we're told about by alpha users and get bugs triaged, fixes written, reviewed and landed in time for the branch point 1 week later are likely to be small enough that they wouldn't be hard to port to the branch (especially right after the branch happens, when diffs between mozilla-central and branch are minimal).
Do we believe that there will be large numbers of such small fixes based on alpha feedback? If not, it seems to me that it would be better to branch either earlier (to get mozilla-central open sooner, and to get non-blocker patches off the 1.9.2 path to reduce risk to 1.9.2) or later (to really have time to get mozilla-central more stabilized before branching). Or were there other reasons for a 1-week interval?
