OK ... soo ... just to make sure I understand. The procedure should be:

1. See Code Push in dw_maintenance.


2. Run cvsreport -update


3. Run cvs/dw-free/hg tags - note Tag info


4. Wait one week or so.


5. Run cvs/dw-free/hg tags -
   
   • a. If highest (non-tip?) tag is different, wait one week more and repeat step.
   
   
   • b. If highest tag matches, proceed.


6. Copy all config files to cvs/< my journal local >/etc/
   
   • a. Do this for any file I've modified in the code, like schemes, etc? - copied into their own cvs/< my journal local >/< original path >?
   
   
   • b. Do schemes follow the same "override with -local" effect as the config files? If I've modified vertical-gradation heavily, will it be overwritten with a code-push? Will gradation-vertical-local override gradation-vertical?


7. Run "hg update -r [tagname]"


8. Run diff on the files in cvs/< my journal local >/etc/config* to make sure none of my changes will be overwritten - any overwritten changes should be moved to a -local.pl file.


9. sudo /etc/init.d/apache2 stop


10. cd $LJHOME


11. run cvsreport.pl without arguments to get a preview of changes being implemented


12. bin/cvsreport.pl -sync -cvsonly


13. bin/cvsreport.pl -sync -cvsonly


14. LJHOME/bin/upgrading/update-db.pl -r -p --innodb


15. $LJHOME/bin/upgrading/update-db.pl -r --cluster=all --innodb


16. $LJHOME/bin/upgrading/texttool.pl load


17. start apache

Does that look right? I could also, I assume, create the update scripts in the Dev_Maintenance wiki (where a lot of this info came from) and replace the relevant parts in my list here.