Webtools:CVS Guidelines: Difference between revisions

Jump to navigation Jump to search
no edit summary
mNo edit summary
No edit summary
Line 6: Line 6:
= Tagging for production =
= Tagging for production =
* Tag your last-known-working-copy as your ROLLBACK (if one doesn't already exist)
* Tag your last-known-working-copy as your ROLLBACK (if one doesn't already exist)
<code>
[morgamic@khan aus]$ cvs tag -f AUS2_ROLLBACK
[morgamic@khan aus]$ cvs tag -f AUS2_ROLLBACK
</code>
* Review LXR logs to make sure each update makes sense
* Review LXR logs to make sure each update makes sense
* Apply your patches for the next batch
* Apply your patches for the next batch
* When you're _SURE_ that this is the final batch of updates, you need to tag it as PRODUCTION, then check that baby in  
* When you're _SURE_ that this is the final batch of updates, you need to tag it as PRODUCTION, then check that baby in  
<code>
[morgamic@khan aus]$ cvs tag -F AUS2_PRODUCTION
[morgamic@khan aus]$ cvs tag -F AUS2_PRODUCTION
cvs tag: Tagging .
cvs tag: Tagging .
T README
T README
T htaccess.dist
T htaccess.dist
T index.php
T index.php
cvs tag: Tagging inc
cvs tag: Tagging inc
T inc/aus.class.php
T inc/aus.class.php
T inc/config-dist.php
T inc/config-dist.php
T inc/init.php
T inc/init.php
T inc/patch.class.php
T inc/patch.class.php
T inc/update.class.php
T inc/update.class.php
T inc/xml.class.php
T inc/xml.class.php
[morgamic@khan aus]$ cvs ci
[morgamic@khan aus]$ cvs ci
</code>


= Pushing updates into production =
= Pushing updates into production =
Line 39: Line 35:
* Always be available after updates are pushed
* Always be available after updates are pushed
* Sysadmins, if the developer did things right, you should be able to rollback by using:
* Sysadmins, if the developer did things right, you should be able to rollback by using:
<code>
[root@khan aus]$ cvs up -r AUS2_ROLLBACK
[root@khan aus]$ cvs up -r AUS2_ROLLBACK
</code>
3,035

edits

Navigation menu