summaryrefslogtreecommitdiff
path: root/pod/perlpolicy.pod
diff options
context:
space:
mode:
authorSteve Hay <steve.m.hay@googlemail.com>2015-02-26 13:20:09 +0000
committerSteve Hay <steve.m.hay@googlemail.com>2015-03-06 08:15:58 +0000
commita969a3c5c3f9d9395fbcacd501f00ddda31745b3 (patch)
tree32a80ea35722a5cb0e9a456aa88f1756236f1a92 /pod/perlpolicy.pod
parenta6f834144147a61af3bf0f2e53c4d9e57518a41d (diff)
downloadperl-a969a3c5c3f9d9395fbcacd501f00ddda31745b3.tar.gz
maint policy: Move paragraph about controversial changes
The point was also raised during discussions over whether to include perlunicook.pod in 5.20.2 that exceptions can be made to the rules under the terms of "Rule 2" and the fact that the pumpking is acting on Larry's behalf. However, this is probably best left being implicit, rather than explicitly stating it. Exceptions should be exceptional; we don't want to encourage them!
Diffstat (limited to 'pod/perlpolicy.pod')
-rw-r--r--pod/perlpolicy.pod7
1 files changed, 4 insertions, 3 deletions
diff --git a/pod/perlpolicy.pod b/pod/perlpolicy.pod
index 6ee4b1e95a..e93edf045b 100644
--- a/pod/perlpolicy.pod
+++ b/pod/perlpolicy.pod
@@ -251,9 +251,6 @@ no longer ship with Perl, but will continue to be available on CPAN.
=head1 MAINTENANCE BRANCHES
New releases of maint should contain as few changes as possible.
-If there is any question about whether a given patch might merit
-inclusion in a maint release, then it almost certainly should not
-be included.
The following types of change may be considered acceptable, as long as they do
not also fall into any of the "unacceptable" categories set out below:
@@ -334,6 +331,10 @@ Those belong in the next stable series.
=back
+If there is any question about whether a given patch might merit
+inclusion in a maint release, then it almost certainly should not
+be included.
+
=head2 Getting changes into a maint branch
Historically, only the pumpking cherry-picked changes from bleadperl