Make the release steps less prone to interpretation :)

[gitmo/Moose.git] / lib / Moose / Manual / Contributing.pod

diff --git a/lib/Moose/Manual/Contributing.pod b/lib/Moose/Manual/Contributing.pod
index a30cc0a..2b2db45 100644 (file)
--- a/lib/Moose/Manual/Contributing.pod
+++ b/lib/Moose/Manual/Contributing.pod
@@ -224,7 +224,8 @@ defend your change.
     git checkout stable
     git merge master # must be a fast forward
     git push both
-    # ship & tag
+    shipit # does not ship the tarball, but does everything else
+    cpan-upload ~/shipit-dist/Moose-X.YZ.tar.gz
 
 Development releases are made without merging into the stable branch.
 
@@ -241,11 +242,11 @@ of effort into supporting older 5.8.x releases.
 
 For major releases which include an API change or deprecation, you should run
 the F<cpan-stable-smolder> script from the L<moose-dev-utils
-repository|gitmo@jules.scsys.co.uk:moose-dev-utils.git>. This script tests a
+repository|gitmo@git.moose.perl.org:moose-dev-utils.git>. This script tests a
 long list of MooseX and other Moose-using modules from CPAN. In order to run
 this script, you must arrange to have the new version of Moose and/or
 Class::MOP in Perl's include path. You can install the module, or fiddle with
-the C<PERL5LIB> env var, whatever makes you happy.
+the C<PERL5LIB> environment variable, whatever makes you happy.
 
 The smolder script downloads each module from CPAN, runs its tests, and logs
 failures and warnings to a F<cpan-stable-smolder.log> file. If there are