Difference between revisions of "Development:Planning:Branching for Camino 2.0"
Jump to navigation
Jump to search
(→Other: add version number, t-c changes) |
(→Files: linky) |
||
| Line 6: | Line 6: | ||
==Files== | ==Files== | ||
| − | * mozilla/client.mk (will need to track any Core changes following branching) | + | * mozilla/client.mk (will need to track any Core changes following branching) [http://pastebin.mozilla.org/659511] [http://pastebin.mozilla.org/659512] (for reference) |
* mozilla/camino | * mozilla/camino | ||
* mozilla/tools/tinderbox-configs/camino | * mozilla/tools/tinderbox-configs/camino | ||
Revision as of 19:33, 25 June 2009
This page exists to provide a repository for requirements, notes, and other information relating to branching CVS trunk in order to support ongoing development for features out-of-scope for Camino 2 while providing a stable branch for the completion for Camino 2 and its subsequent security and stability updates.
Schedule
- Mid-late June, following the end of releasemania
Files
- mozilla/client.mk (will need to track any Core changes following branching) [1] [2] (for reference)
- mozilla/camino
- mozilla/tools/tinderbox-configs/camino
Other
- Update cb-xserve01 and probably cb-minibinus01 to pull/build CAMINO_2_0_BRANCH code and tinder-configs
- Update 2.0 branch tinder-configs for branch name
- Update trunk tinder-configs for Cm2.1-M1.9
- Update version number on trunk to 2.1a1pre
- Committers should use a local wrapper for cross-commit to provide branch args
- Socorro
- "Branch" field in Bugzilla will need something for 2.0.x branch
- Update status whiteboard docs for [camino-2.0] whiteboard entries
