From 193c036fef02471f232a40b72cc8120893056d35 Mon Sep 17 00:00:00 2001 From: Steve Hay Date: Fri, 28 Mar 2014 22:05:29 +0000 Subject: [PATCH] RMG - refer to BLEAD-POINT/BLEAD-FINAL releases for consistency and clarity --- Porting/release_managers_guide.pod | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod index 741b337..9da9300 100644 --- a/Porting/release_managers_guide.pod +++ b/Porting/release_managers_guide.pod @@ -215,17 +215,17 @@ you made a local CPAN mirror. Note that a minicpan mirror won't actually work, but can provide a good first pass to quickly get a list of modules which definitely haven't changed, to avoid having to download absolutely everything. -For a BLEAD release with 'cpan' upstream, if a CPAN release appears to be ahead -of blead, then consider updating it (or asking the relevant porter to do so). -(However, if this is one of the last BLEAD releases before a BLEAD-FINAL -release and hence blead is in some kind of "code freeze" state (e.g. the -sequence might be "contentious changes freeze", then "user-visible changes -freeze" and finally "full code freeze") then any CPAN module updates must be -subject to the same restrictions, so it may not be possible to update all -modules until after the BLEAD-FINAL release.) If blead contains edits to a -'cpan' upstream module, this is naughty but sometimes unavoidable to keep blead -tests passing. Make sure the affected file has a CUSTOMIZED entry in -F. +For a BLEAD-POINT or BLEAD-FINAL release with 'cpan' upstream, if a CPAN +release appears to be ahead of blead, then consider updating it (or asking the +relevant porter to do so). (However, if this is a BLEAD-FINAL release or one of +the last BLEAD-POINT releases before it and hence blead is in some kind of +"code freeze" state (e.g. the sequence might be "contentious changes freeze", +then "user-visible changes freeze" and finally "full code freeze") then any +CPAN module updates must be subject to the same restrictions, so it may not be +possible to update all modules until after the BLEAD-FINAL release.) If blead +contains edits to a 'cpan' upstream module, this is naughty but sometimes +unavoidable to keep blead tests passing. Make sure the affected file has a +CUSTOMIZED entry in F. If you are making a MAINT release, run C on both blead and maint, then diff the two outputs. Compare this with what you expect, and if -- 2.7.4