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

diff --git a/pod/perlpolicy.pod b/pod/perlpolicy.pod
index 44fb99f..063dae5 100644 (file)
--- 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.