ReleaseEngineering/How To/Request a New Repository: Difference between revisions

add which IT component to use
(Initial content)
 
(add which IT component to use)
Line 28: Line 28:


# Ensure request is complete, including determination of need for RelEng services over the life of the project. Continue....
# Ensure request is complete, including determination of need for RelEng services over the life of the project. Continue....
# If no RelEng services are required, annotate the bug to that effect, and forward to IT for implementation. Requester notified when IT creates repository and resolves bug as fixed. DONE
# If no RelEng services are required, annotate the bug to that effect, and forward to IT* for implementation. Requester notified when IT creates repository and resolves bug as fixed. DONE
# If RelEng services are required, RelEng will file related tickets for both short term and long term service needs. One of those tickets will be the IT bug for repository creation. Continue....
# If RelEng services are required, RelEng will file related tickets for both short term and long term service needs. One of those tickets will be the IT* bug for repository creation. Continue....
# When RelEng is notified of repository availability, perform any remaining RelEng service setup. Notify requester by resolving bug as fixed when everything is ready. DONE
# When RelEng is notified of repository availability, perform any remaining RelEng service setup. Notify requester by resolving bug as fixed when everything is ready. DONE
<small><nowiki>*</nowiki> IT component to use is: <em>Server Operations: Developer Services</em></small>


Note: the assumption is that only RelEng coordination is needed. If other groups wish approval, coordination, they would be looped in here.
Note: the assumption is that only RelEng coordination is needed. If other groups wish approval, coordination, they would be looped in here.
Confirmed users
1,351

edits