3,035
edits
No edit summary |
|||
| Line 10: | Line 10: | ||
* Don't file IT requests for production updates every hour, and don't email them every 5 minutes (or text-message them either) -- your best bet is to group your updates and push them weekly. | * Don't file IT requests for production updates every hour, and don't email them every 5 minutes (or text-message them either) -- your best bet is to group your updates and push them weekly. | ||
= Tagging for | = Tagging for Staging = | ||
* Check in all the updates/patches you're going to stage. | |||
* Add the STAGING tag to the code you want to stage: | |||
[morgamic@khan aus]$ cvs up -dP | |||
[morgamic@khan aus]$ cvs ci -m 'some message' | |||
[morgamic@khan aus]$ cvs tag -F AUS2_STAGING | |||
= Tagging for Production = | |||
* Check in all the updates/patches you're going to check in. | * Check in all the updates/patches you're going to check in. | ||
* When you're ready to do a release-to-production rollup, make sure you have a current copy of the source, and tag is with the current date, including the hour/minute: | * When you're ready to do a release-to-production rollup, make sure you have a current copy of the source, and tag is with the current date, including the hour/minute: | ||
| Line 45: | Line 52: | ||
[morgamic@khan aus]$ cvs diff -rAUS2_PRODUCTION -rAUS2_RTM_200608081426 | [morgamic@khan aus]$ cvs diff -rAUS2_PRODUCTION -rAUS2_RTM_200608081426 | ||
[morgamic@khan aus]$ # Should be no output. | [morgamic@khan aus]$ # Should be no output. | ||
= General Rules = | |||
* Whatever is checked out in staging always has the _STAGING tag on it at all times | |||
* Whatever is checked out in production always has the _PRODUCTION tag on it at all times | |||
* Any previous _PRODUCTION tag should be tagged w/ an RTM_DATE tag before moving on to the next _PRODUCTION tag | |||
= When to push = | = When to push = | ||
edits