Click here to return to top level Code Management page.
Subject: Jetstream Code Synchronization Kickoff
Hi Everyone,
It’s time again to start the Jetstream code update process. After the current round of merging and testing activities are complete, a new baseline version of Jetstream will be available. I will send emails to all group members containing instructions for running test cases and updating to the new baseline version of Jetstream. Please note that it is mandatory that all group members update their version of Jetstream on a regular basis.
If your name is on the following list then you are part of this month’s Jetstream Code Update group. If this is the case, read on for instructions on how to proceed with the code updating process. NOTE: The procedure is to be performed by each member of the current Jetstream Code Update group, one at a time, in the order prescribed by the following list:
Tim Chau
Gregg Streuber
Tom Reist
Member 1 starts by pulling from sync staging area, merging locally (possibly including resolving merge conflicts) then pushing back to sync staging area. Note: as part of the local merge process, please ensure that all compiling issues are resolved before pushing back to the sync staging area.
The following steps describe the pull/merge/push procedure to be performed on Scinet by each member of the current merge group:
Commit any pending changes to your master branch before beginning the merge process:
git checkout master
git commit -a
Create a branch for merging:
git branch merge
Switch to merge branch so that your local master branch is not affected during merge:
Subject: Jetstream Code Synchronization Kickoff
Hi Everyone,
It’s time again to start the Jetstream code update process. After the current round of merging and testing activities are complete, a new baseline version of Jetstream will be available. I will send emails to all group members containing instructions for running test cases and updating to the new baseline version of Jetstream. Please note that it is mandatory that all group members update their version of Jetstream on a regular basis.
If your name is on the following list then you are part of this month’s Jetstream Code Update group. If this is the case, read on for instructions on how to proceed with the code updating process. NOTE: The procedure is to be performed by each member of the current Jetstream Code Update group, one at a time, in the order prescribed by the following list:
Member 1 starts by pulling from sync staging area, merging locally (possibly including resolving merge conflicts) then pushing back to sync staging area. Note: as part of the local merge process, please ensure that all compiling issues are resolved before pushing back to the sync staging area.
The following steps describe the pull/merge/push procedure to be performed on Scinet by each member of the current merge group:
Member 2, then member 3, then member 4 (in sequence) repeat the pull/merge/push steps described above.
Final member, please email me when the merge process is complete.
Thanks for your cooperation,
<Gatekeeper>