Webtools:SVN Guidelines: Difference between revisions

Jump to navigation Jump to search
Line 38: Line 38:
* When you're '''SURE''' that the patches are correct/make sense, you need to commit it (substitute your rev # for 150):  
* When you're '''SURE''' that the patches are correct/make sense, you need to commit it (substitute your rev # for 150):  
  [clouserw@fattony /data/mozilla.com]$ svn commit -m "Merging revisions 100:150 /trunk/ into /tags/production/"
  [clouserw@fattony /data/mozilla.com]$ svn commit -m "Merging revisions 100:150 /trunk/ into /tags/production/"
* Then make a snapshot tag for easy reference:
[clouserw@fattony ~]$ svn copy -r 150 svn+ssh://svn.mozilla.org/projects/mozilla.com/trunk svn+ssh://svn.mozilla.org/projects/mozilla.com/tags/prod_`date +%Y%m%d%H%M` -m "Creating snapshot tag of /trunk/ at r150"


= When to push =
= When to push =
Line 47: Line 45:
= Requesting an update in production =
= Requesting an update in production =
* [https://bugzilla.mozilla.org/enter_bug.cgi?format=it_request&product=mozilla.org File an IT Request] when you are sure you are ready to go
* [https://bugzilla.mozilla.org/enter_bug.cgi?format=it_request&product=mozilla.org File an IT Request] when you are sure you are ready to go
* '''Include in the request the path to the previous snapshot tag, so an easy rollback can occur!''' Also include any other rollback instructions.
* '''Include in the request the revision number of the previous merge, so an easy rollback can occur!''' Also include any other rollback instructions.
* Assign the appropriate severity -- note that critical or blocker pages the oncall.
* Assign the appropriate severity -- note that critical or blocker pages the oncall.


Confirmed users, Bureaucrats and Sysops emeriti
1,737

edits

Navigation menu