Confirmed users
142
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 07:46, 4 June 2014
, 4 June 2014no edit summary
(add location of hook list) |
No edit summary |
||
| Line 67: | Line 67: | ||
# negotiate details with the dev team, but ensure the top directory is appropriate for releng mapping of repositories | # negotiate details with the dev team, but ensure the top directory is appropriate for releng mapping of repositories | ||
# file new bugs for any changes needed to support the repository | # file new bugs for any changes needed to support the repository | ||
# if no post-repository-creation steps are needed, reassign bug to "Server Operations: Developer | # if no post-repository-creation steps are needed, reassign bug to Product: "mozilla.org", Component: "Server Operations: Developer Services" | ||
# otherwise, open a new bug for the repository creation, and all supporting activities releng needs to do | # otherwise, open a new bug for the repository creation, and all supporting activities releng needs to do | ||
| Line 89: | Line 89: | ||
# ensure repository name is in a non-RelEng namespace (top level directory) | # ensure repository name is in a non-RelEng namespace (top level directory) | ||
#* ssot to be linked later; currently releng "owns" (null), releases, integration, projects, and build. | #* ssot to be linked later; currently releng "owns" (null), releases, integration, projects, and build. | ||
# reassign the request to | # reassign the request to Product: "mozilla.org", Component: "Server Operations: Developer Services" | ||
= General Notes = | = General Notes = | ||