Webtools:SVN Guidelines: Difference between revisions

Jump to navigation Jump to search
Line 24: Line 24:
** Code for both should always be from the same production tag.
** Code for both should always be from the same production tag.
** (Programmers should be developing and testing on their own branches, or /trunk/)
** (Programmers should be developing and testing on their own branches, or /trunk/)
* When code is merged into production, a tag is created at the same time with the following format: $description_$datetime, eg. prod_200610241902


= Tagging for Staging / Production =
= Tagging for Staging / Production =
Line 39: 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 =
Confirmed users, Bureaucrats and Sysops emeriti
1,737

edits

Navigation menu