Gatekeepers+Guide+to+Jetstream+Code+Management

Click here to return to top level Code Management page.

The following procedure describes the steps to be performed by the official maintainer of the Jetstream code repository (the "Gatekeeper") to execute the monthly Jetstream group code update.

Email reminder to upcoming Jetstream Code Update group

 * Gatekeeper to email upcoming merge group telling them to get their code ready for the merge.
 * It will suggest that any recently added code in good working order be moved over to their master branch in anticipation of the upcoming merge.
 * Click here to see an example email.

Initialize Sync Staging Area
code git clone --bare howard@oddjob.utias.utoronto.ca:/nfs/carv/d1/people/comp-aero/jetstream.git jetstream_sync_staging_yyyymmdd
 * Gatekeeper to create sync staging area by cloning the central repo to his home directory on SciNet:

code code chmod -R g+rwx jetstream_sync_staging_yyyymmdd code
 * Gatekeeper to set permissions to allow merge group to write to sync staging area:

**Email Jetstream Code Update Kickoff notification to entire Jetstream Developers group**
 * Gatekeeper to send an email to entire group to kickoff the merge process with instructions on how to proceed
 * The email will specify the names of the current merge group. The email will inform the entire group of a tentative synchronization date.
 * merge group commences merging process
 * Click here to see an example email

Add a new link to the "Jetstream Merge Notes" page on utoronto-comp-aero wiki

 * Create a link to a new "Merge Notes" page
 * Use "Merge Notes" page template
 * Click here to go to Jetstream Merge Notes page

Entire Jetstream Developers group to commence Jetstream code testing activities

 * Click here to see an example email
 * Each group member will run their assigned test case(s) and debug as required
 * Group members will update the status of their test case(s) on the Jetstream Test Suite Summary Spreadsheet (Gatekeeper is owner of this Google Docs spreadsheet)
 * If there are discrepancies in test case results, work with group member to resolve discrepancies

Update Jetstream central repository
code git push central :master code
 * Gatekeeper to pull any changes from jetstream sync staging area to his testing branch
 * Gatekeeper to push changes from his testing branch to central repo:

Email Jetstream Code Update notification to entire Jetstream Developers group

 * Click here to see an example email