From: Vincent Pit Date: Sat, 18 Jul 2009 21:31:25 +0000 (+0200) Subject: Fix some nits in release_managers_guide.pod X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=ce4f4fe21306fe15b2fbafac14eb81691d0b304a;p=p5sagit%2Fp5-mst-13.2.git Fix some nits in release_managers_guide.pod --- diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod index edf5ed9..1e36a48 100644 --- a/Porting/release_managers_guide.pod +++ b/Porting/release_managers_guide.pod @@ -81,7 +81,7 @@ F with the current date, e.g. 5.8.9-RC1 2008-Nov-10 -Make sure the correct pumpking is listed, and if this your first time, +Make sure the correct pumpking is listed, and if this is your first time, append your name to C. =item * @@ -348,7 +348,7 @@ final release, remove it. [ XXX how now?? see 34813 for old way ] Update C. -Note that is this is a maint release, you should run the following actions +Note that if this is a maint release, you should run the following actions from the maint directory, but edit the C in I and subsequently cherry-pick it. @@ -389,15 +389,13 @@ This creates a file that looks something like ... ); -No - Cut and paste these tables into F: the module version list should be appended as the last entry in the C<%version> hash (or replaced, if we've already added it for an earlier release candidate), while the existing C<%upstream> and C<%bug_tracker> hashes should be replaced with the new versions. -Edit the version number in the new C<<'Module::CoreList' => 'X.YZ'>> +Edit the version number in the new C<< 'Module::CoreList' => 'X.YZ' >> entry, as that is likely to reflect the previous version number. Then, add the current perl version to the C paragraph. @@ -504,7 +502,7 @@ on the previous filename to look for suitable candidates. =item * -If this was major release, bump the version, e.g. 5.12.0 to 5.13.0 +If this was a major release, bump the version, e.g. 5.12.0 to 5.13.0 [ XXX probably more complex stuff to do, including perldelta, C ]