761
edits
User:Jprosevear/RapidReleaseUpdate: Difference between revisions
User:Jprosevear/RapidReleaseUpdate (view source)
Revision as of 15:58, 31 March 2011
, 31 March 2011→Release Driver and Mechanices Process Meetings [legneato, smooney]
Jprosevear (talk | contribs) |
Jprosevear (talk | contribs) |
||
| Line 48: | Line 48: | ||
This section documents key discussion points and proposals that are in progress or need to happen. It also notes anything unclear. Where possible it documents owners who need to give input and/or drive the item to conclusion. | This section documents key discussion points and proposals that are in progress or need to happen. It also notes anything unclear. Where possible it documents owners who need to give input and/or drive the item to conclusion. | ||
=== Release | === Release [legneato, smooney] === | ||
* When are meetings about go/no-go and decisions about what to turn off made? | * When are meetings about go/no-go and decisions about what to turn off made? | ||
* How to manage 3 in-flight release paths at once | * How to manage 3 in-flight release paths at once | ||
==== L10N and I18N [legneato, smooney, axel, choffman, christian] ==== | ==== L10N and I18N [legneato, smooney, axel, choffman, christian] ==== | ||
| Line 58: | Line 56: | ||
* l10n repository naming | * l10n repository naming | ||
==== Branch Merging | == Repository Mechanics == | ||
* | |||
=== Branch Naming === | |||
How to name branches, particularly release branches. | |||
* Branch naming proposal John O'D | |||
** http://groups.google.com/group/mozilla.dev.planning/msg/30c67403ddad9a7e | |||
=== Merging === | |||
How to do the merge to downstream branches from a mechanical standpoint. | |||
* Do not delete experimental, merge from m-c | |||
* track to see how much of a problem we get with backouts/preffing off | * track to see how much of a problem we get with backouts/preffing off | ||
* the first merges will be manageable | * the first merges will be manageable | ||