summaryrefslogtreecommitdiff
path: root/Porting
diff options
context:
space:
mode:
authorDavid Mitchell <davem@iabyn.com>2013-05-07 17:53:49 +0100
committerDavid Mitchell <davem@iabyn.com>2013-05-07 17:53:49 +0100
commit74648505dad13815ce0f54647c8c26a3ea975312 (patch)
tree89354505eae72e9a089c52270cd945d86e6fb749 /Porting
parent89781932edba932563a4afd250fc5759417cf958 (diff)
downloadperl-74648505dad13815ce0f54647c8c26a3ea975312.tar.gz
RMG: say that for maint there are two RMG versions
Diffstat (limited to 'Porting')
-rw-r--r--Porting/release_managers_guide.pod7
1 files changed, 7 insertions, 0 deletions
diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod
index 7b14606078..e39534c202 100644
--- a/Porting/release_managers_guide.pod
+++ b/Porting/release_managers_guide.pod
@@ -96,6 +96,13 @@ changes since.
It's essentially the same procedure as for making a release candidate, but
with a whole bunch of extra post-release steps.
+Note that for a maint release there are two versions of this guide to
+consider: the one in the maint branch, and the one in blead. Which one to
+use is a fine judgement. The blead one will be most up-to-date, while
+it might describe some steps or new tools that aren't applicable to older
+maint branches. It is probably best to review both versions of this
+document, but to most closely follow the steps in the maint version.
+
=item A blead point release (BLEAD-POINT)
A release with an odd version number, such as 5.15.0 or 5.15.1.