Release:Release Automation on Mercurial:Starting a Release: Difference between revisions

no edit summary
No edit summary
Line 5: Line 5:
= L10N Changesets =
= L10N Changesets =
Currently we have separate changesets files for Fennec and Firefox. Both are generated from the [https://l10n.mozilla.org/shipping/milestones l10n dashboard]<br />
Currently we have separate changesets files for Fennec and Firefox. Both are generated from the [https://l10n.mozilla.org/shipping/milestones l10n dashboard]<br />
First log in to the dashboard with your LDAP and then follow the instructions below
If you need changesets for a subsequent build (eg. beta1 build #2), copy them from the previous ship-it request.<br />
First log in to the dashboard with your LDAP and then follow the instructions below.


== Create milestones ==
== Create milestones ==
Line 15: Line 16:
** For '''final releases''' clear the first field, remove "_beta_b#" from the second field, and append ".0" (or .0.1).
** For '''final releases''' clear the first field, remove "_beta_b#" from the second field, and append ".0" (or .0.1).
* hit "submit" and the milestones will be created.
* hit "submit" and the milestones will be created.
If you need the milestones for a subsequent build (eg. beta1 build #2), copy them from the previous ship-it request.


Note: you cannot create release milestones for an older major version.  For example, when 18.x is current, 17.x milestones cannot be created.  This is especially relevant for Thunderbird's slower release cycle.  In that case, use the existing changesets from the l10n-changesets_thunderbird-release file.
Note: you cannot create release milestones for an older major version.  For example, when 18.x is current, 17.x milestones cannot be created.  This is especially relevant for Thunderbird's slower release cycle.  In that case, use the existing changesets from the l10n-changesets_thunderbird-release file.
canmove, Confirmed users
6,439

edits