summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAaron Crane <arc@cpan.org>2015-11-15 15:10:54 +0000
committerSteve Hay <steve.m.hay@googlemail.com>2015-11-19 13:16:19 +0000
commit83e412526f3e30fa8c5b20c31a2269c6ce286d00 (patch)
tree51826f731dfc476a06aa98bfd67ba05643798d56
parent826a863e696ebe18115c5ce7cb7a2c9898081ba6 (diff)
downloadperl-83e412526f3e30fa8c5b20c31a2269c6ce286d00.tar.gz
maint policy: allow fixes for new features
As (Steve Hay)++ said on-list: I think it's a shame if users get a 5.X.0 release with some shiny new features which I hope they're excited about and start making use of, but then find bugs in those features and have to wait until 5.X+2.0, rather than 5.X.1, for fixes. rjbs++ clarified that, although such changes constitute a break in backwards compatibility, there are two reasons why bugs in new features should be fixed in maint: * they delay people from using a feature for a year, because it does something stupid * they risk enshrining bad behavior under the usual program of bugward compatibility (cherry picked from commit 539a060caed4755d586113e0125241cc88d1048e)
-rw-r--r--pod/perlpolicy.pod5
1 files changed, 5 insertions, 0 deletions
diff --git a/pod/perlpolicy.pod b/pod/perlpolicy.pod
index 44fb99fb0b..063dae5114 100644
--- a/pod/perlpolicy.pod
+++ b/pod/perlpolicy.pod
@@ -291,6 +291,11 @@ upgrade from very old versions of perl to the latest version.
=item *
+Patches that fix bugs in features that were new in the corresponding 5.x.0
+stable release.
+
+=item *
+
Patches that fix anything which prevents or seriously impacts the build
or installation of perl.