Thunderbird:Thunderbird3:Final: Difference between revisions
Jump to navigation
Jump to search
Line 85: | Line 85: | ||
* New hg repo | * New hg repo | ||
** Should have base branch tag. | ** Should have base branch tag. | ||
** Tag and clone hg repo - IT needs to do the clone (file bug in mozilla.org/Server Operations) {{Bug| | ** Tag and clone hg repo - IT needs to do the clone (file bug in mozilla.org/Server Operations) {{Bug|522460}} | ||
** mxr - new repo search required e.g. {{Bug|510495}} | ** mxr - new repo search required e.g. {{Bug|510495}} | ||
* Nagios monitoring | * Nagios monitoring |
Revision as of 12:18, 15 October 2009
Thunderbird » Thunderbird 3 » »Development Roadmap
Thunderbird 3 Final
Drivers & Leads (RC1 & through to final)
- Standard8 is release driver
- gozer is build engineer
- _Tsk_ is QA
- sipaq is L10N (for builds) co-ordinator
- rebron is Website & Publicity co-ordinator
- Pascal is Website L10N co-ordinator
Thunderbird 3 Release Candidate 1
Dates & Blocking
- Approvals
- Start TBD
- Only blocking & approved patches allowed.
- Need to create flag - approval-thunderbird3
- Planned Freeze Dates - Updated ( All dates use time of 23:59 PST )
- Slushy String freeze date: TBD
- Slushy Code Freeze date: TBD
- Firm String / Code freeze date: TBD
- l10n-mozilla-1.9.1 freeze date: TBD
- Target Build Ship date: TBD
- Blockers/Wanted
- Proposed Blocking
- Fixed:
Details
- Release TB builds (full QA etc)
- Test Beta -> RC update, first test channel, then beta channel
- We will also need to test 2.x -> 3 (_Tsk_)
- Do we need an alternate start page for RC builds?
- Don't think so - but we need to be able to distinguish RC1/RC2 (_Tsk_)
Thunderbird 3 Final
Gecko 1.9.1 version
- 1.9.1.4 ideal base.
- Keep an eye on
Release
- Website & L10N
- Servers
- Statistics
Major updates
Firefox are doing:
- Manual update only initially - user has to request Tools -> Update.
- Automatic updates - at the first security release if happy to do so.
Post Release
- Stabilise language pack versions - port bug 505491
Plans
Branching
Tracking Bug: bug 522211
HgPollers ready (split for trunk + branch detection) bug 489352- New hg repo
- Should have base branch tag.
- Tag and clone hg repo - IT needs to do the clone (file bug in mozilla.org/Server Operations) bug 522460
- mxr - new repo search required e.g. bug 510495
- Nagios monitoring
- Graph server?
- client.py - bug 522445
- Note: bug 504143 was m-c branch for 1.9.2 tracking bug.
Plans to be made
- Point Releases
- Approvals/Blocking process post release
- How to do firedrill/maintenance updates: