For a general list of planning and status pages for each functional
group of the Mozilla platform see:
http://wiki.mozilla.org/Platform
General Agenda:
* Status updates on feature development (both front-end and platform)
* Identifying areas of code risk for upcoming milestones
* Discussion of security review impacts, standards/spec compliance
work, internal and external dependencies
Meeting Details:
* Agenda: http://wiki.mozilla.org/Platform/2008-11-25
* Tue, November 25, 11:00 am PDT
* 650-903-0800 x92 Conf# 8605 (US/INTL)
* 1-800-707-2533 (pin 369) Conf# 8605 (US)
* join irc.mozilla.org #shiretoko for back channel
Cheers,
Damon
- checkin rules for mozilla-central once it re-opens after tagging
for beta 2
- dates for merging mozilla-central over to mozilla-1.9.1
- actual branching date where we switch over to mozilla-1.9.1
For consideration, there's a logjam of patches for blocking bugs
waiting to go in after beta 2; David Baron and others have suggested
that we continue to use mozilla-central until EOD Thursday, at which
point we'd remerge mozilla-central to mozilla-1.9.1 and make the
switch. This would prevent the need for a large set of double landings
for those blockers. The proposal I'd like to work with is:
- after tagging for beta 2, mozilla-central will be open only to
blocking-firefox3.1, blocking1.9.1, and approval1.9.1
- merge to mozilla-1.9.1 repo EOD Thursday
- after merge, the mozilla-1.9.1 repo will be open only to blocking-
firefox3.1, blocking1.9.1, and approval1.9.1; mozilla-central will be
back to usual tree rules of requiring review only
Concerns:
- how can we make sure to watch performance on mozilla-central post-
merge
- is tue-thu enough time for the logjam to get through
cheers,
mike
> _______________________________________________
> dev-planning mailing list
> dev-pl...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-planning