SeaMonkey/StatusMeetings/2008-08-12: Difference between revisions

Jump to navigation Jump to search
Line 37: Line 37:
** Standard8: TB 30.b1 code freeze is currently set for 9th September. How about we aim SM 2.0a1 alpha code freeze for that date? We can then send out emails to all those currently doing those bugs saying this is the target date, if you can't manage it, please let us know so we can move things forward so it essentially gives us 4 weeks.
** Standard8: TB 30.b1 code freeze is currently set for 9th September. How about we aim SM 2.0a1 alpha code freeze for that date? We can then send out emails to all those currently doing those bugs saying this is the target date, if you can't manage it, please let us know so we can move things forward so it essentially gives us 4 weeks.
* Blocker triage?
* Blocker triage?
** we have 32 blocking? requests to triage.
** We have 32 blocking? requests to triage.
** The deadline for triage to be completed should be early enough so we can address all blocking+ bugs before the release.
** From https://wiki.mozilla.org/Thunderbird:Shredder_a2#Flags "What should block alpha2? Not very much; mostly things that would truly impair usability on a day-to-day basis. dataloss bugs, crashers, and bugs with serious usability impact are likely to qualify."


=== Mercurial ===
=== Mercurial ===
Confirmed users
2,595

edits

Navigation menu