[Pidgin] ReleaseProcess modified
Pidgin
trac at pidgin.im
Wed Jul 4 00:13:02 EDT 2012
Changed page "ReleaseProcess" by QuLogic from 65.92.148.72*
Page URL: <http://developer.pidgin.im/wiki/ReleaseProcess>
Diff URL: <http://developer.pidgin.im/wiki/ReleaseProcess?action=diff&version=58>
Revision 58
Comment: More mtn->hg stuff
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: ReleaseProcess
=========================================================================
--- ReleaseProcess (version: 57)
+++ ReleaseProcess (version: 58)
@@ -22,18 +22,19 @@
= Release =
1. Tag the repository.
{{{
-TAG=v2.6.2 # for example
+VERSION=2.6.2 # for example
+TAG=v$VERSION
hg tag -r $REVISION $TAG
}}}
- 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?)
+ 1. Extract the tagged code
{{{
-mtn -d $DATABASE co -r t:$TAG pidgin-$VERSION
+hg archive -r $TAG ../pidgin-$VERSION
}}}
1. Run {{{./autogen.sh}}}
1. Run {{{make release}}}[[br]]
This will perform the following steps (which can also be done by hand at this point):
a. Run {{{make distcheck}}} (optional; use {{{make packages}}} instead of {{{make release}}} to skip this in automation. It really is a good idea, though!)
- a. Verify that the revision tagged with this version's tag name (v$VERSION) is the same as the revision in the current workspace, and that there are no changes to the current workspace
+ a. Verify that the revision tagged with this version's tag name (v$VERSION) is the same as the revision in the current workspace, and that there are no changes to the current workspace
a. Run {{{make dist-gzip}}} and {{{make dist-bzip2}}}
a. Sign the two tarballs
{{{
-------8<------8<------8<------8<------8<------8<------8<------8<--------
* The IP shown here might not mean anything if the user or the server is
behind a proxy.
--
Pidgin <http://pidgin.im>
Pidgin
This is an automated message. Someone at http://pidgin.im added your email
address to be notified of changes on ReleaseProcess. If it was not you, please
report to .
More information about the Wikiedit
mailing list