Confirmed users
1,364
edits
ReleaseEngineering/How To/Handle A New Repository Request: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/How To/Handle A New Repository Request (view source)
Revision as of 18:34, 1 March 2013
, 1 March 2013be explicit on locations of L10N repos per product
(be explicit on locations of L10N repos per product) |
|||
| Line 53: | Line 53: | ||
Steps (details from l10n side are at [[L10n:Bugogram#hg_repo]]: | Steps (details from l10n side are at [[L10n:Bugogram#hg_repo]]: | ||
* reassign the bug to component "Server Operations: Developer Services" requesting creation of the repositories per locale, with the indicated access level, hooks, as follows: | * reassign the bug to component "Server Operations: Developer Services" requesting creation of the repositories per locale, with the indicated access level, hooks, as follows: | ||
** For Firefox locale: this means creating repos in each of mozilla-aurora, mozilla-beta, mozilla-release, with mxr indexing. | ** For Firefox locale: this means creating repos in each of <tt>/releases/l10n/mozilla-aurora</tt>, <tt>/releases/l10n/mozilla-beta</tt>, <tt>/releases/l10n/mozilla-release</tt>, with mxr indexing. | ||
** For B2G locale: this means creating one repo, with 'no' mxr indexing | ** For B2G locale: this means creating one repo in <tt>/gaia-l10n</tt>, with 'no' mxr indexing | ||
* Notify release that a new locale is on the horizon | * Notify release that a new locale is on the horizon | ||
Done | Done | ||