Oct 5 : Code freeze late evening PDT
Oct 6 : Start build1 of the beta assuming trees are green
Oct 7 : Begin QA testing (or earlier as builds become available)
Oct 13 : Complete QA testing by AM, ship beta in late day PDT
This requires an aggressive push on our remaining P1 blockers:
* there are > 80 unresolved on mozilla-1.9.2 [2]
* only 25 or so are not already fixed on mozilla-central or
tracemonkey [3]
* of those, only a handful don't already have patches or are waiting
to land
Please review the lists below and if you are assigned to or are
reviewing one of the blockers, take some time to take the appropriate
action (land on mozilla-1.9.2, complete your review, follow up on
review comments, etc). If you think that it's unfeasible for you to be
finished by Monday next week, please let me know now - there is no
shame, we're building estimates and timelines, and this is my
assessment after spending some time with the bug lists. You guys know
the bugs, themselves.
We'll revisit this estimate on Thursday evening based on the feedback
I collect.
cheers,
mike
[1]: https://wiki.mozilla.org/Firefox/DeliveryMeetings/2009-09-30
[2]: https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20flag%3Ablocking-firefox3.6%2B%2Cblocking1.9.2%2B%20-status1.9.2:fixed,unaffected,wontfix%20-P2
[3]: https://bugzilla.mozilla.org/buglist.cgi?quicksearch=OPEN%20flag%3Ablocking-firefox3.6%2B%2Cblocking1.9.2%2B%20-status1.9.2:fixed,unaffected,wontfix%20-P2%20-sw:fixed-in-tracemonkey
I'll be back in my office tuesday night, in case all things fail.
Axel
juanb
> _______________________________________________
> dev-planning mailing list
> dev-pl...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-planning
>
I checked with Juan exactly what he meant, since "beta" is so overloaded
as a word, and we often enable updates separately from the official
release. In this case I believe he's advocating a short QA period and
then release it to the world all the ways we can.
-Nick
Several of my tech-savvy friends thought someone had hacked our update
server, called me about it, etc — and proceeded to manually look for a new
version of Firefox from our servers.
It was a case of breaking expectations and confusing people in a weird
manner. While the outcome might have been desirable, we should have a
different execution this time.
--
Alexander Limi · Firefox User Experience · http://limi.net
> Whatever and however we do it, let's not ever call it b99 again.
Absolutely agreed. Let's never do that again. It was particularly
confusing for users in Asia who often have less information to go on
in their own language and led to lots of confusion regarding the
authenticity of that strangely-numbered-beta.
Gen