Changes between Version 56 and Version 57 of ReleaseProcess

Timestamp:

Jul 3, 2012, 6:19:00 AM (12 years ago)

Author:

MarkDoliner

Comment:

Updates for mtn --> hg

ReleaseProcess

@@ -24 +24 @@
 {{{
 TAG=v2.6.2 # for example
-mtn tag $REVISION $TAG
+hg tag -r $REVISION $TAG
 }}}
- 1. Check out the tagged code
+ 1. Check out the tagged code (TODO: What's the best way to do this with hg while checking out/copying/cloning a local repo?)
 {{{
 mtn -d $DATABASE co -r t:$TAG pidgin-$VERSION
@@ -48 +48 @@
  1. Update the Pidgin website
   a. Change inc/version.inc.php (only for full releases, not for betas)
-  a. Update the !ChangeLog in pidgin.im web mtn (this is used by the release notification plugin)
+  a. Update the !ChangeLog in http://hg.pidgin.im/www/pidgin/ (this is used by the release notification plugin)
   a. Update the ChangeLog
  1. Send announcement email to announce and packagers mailing lists (sending to announce also sends to support and devel)
@@ -58 +58 @@
  1. Add new Trac milestone for the next release
  1. "Complete" old milestone 
- 1. Bump the auto-close script to target auto-closed bugs to the new milestone (/srv/trac/developer.pidgin.im/monotone_support/trac-mtn-post-commit-hook.py on imperial)
+ 1. Bump the auto-close script to target auto-closed bugs to the new milestone (/srv/trac/developer.pidgin.im/mercurial_support/trac-hg-post-commit-hook.py on imperial)
  1. Update "The Road to" on WikiStart to list tickets for the new version