diff options
| author | Aaron Crane <arc@cpan.org> | 2015-11-15 15:10:54 +0000 |
|---|---|---|
| committer | Aaron Crane <arc@cpan.org> | 2015-11-19 11:24:40 +0000 |
| commit | 539a060caed4755d586113e0125241cc88d1048e (patch) | |
| tree | dd080e374593be1d0c96d0df26084d2a27762817 | |
| parent | 101d63659b7355370ff8d5a0076c0e456293458e (diff) | |
| download | perl-539a060caed4755d586113e0125241cc88d1048e.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
| -rw-r--r-- | pod/perlpolicy.pod | 5 |
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. |