In perl.git, the branch blead has been updated

<http://perl5.git.perl.org/perl.git/commitdiff/f1126a906c58d54cb68626bd2e4c1d577d77796a?hp=7fcb412668d2fa3df241491ee985370bed3a3018>

- Log -----------------------------------------------------------------
commit f1126a906c58d54cb68626bd2e4c1d577d77796a
Author: Ricardo Signes <[email protected]>
Date:   Mon Sep 15 18:19:41 2014 -0400

    document how to graduate from experimental status

M       pod/perlpolicy.pod

commit ce98a8cbcc62ba1e5eceafb381453aff6ac4471f
Author: Ricardo Signes <[email protected]>
Date:   Mon Sep 15 18:19:28 2014 -0400

    release schedule: Max M. will do December 2014

M       Porting/release_schedule.pod
-----------------------------------------------------------------------

Summary of changes:
 Porting/release_schedule.pod | 2 +-
 pod/perlpolicy.pod           | 8 ++++++++
 2 files changed, 9 insertions(+), 1 deletion(-)

diff --git a/Porting/release_schedule.pod b/Porting/release_schedule.pod
index bd3efba..cceb8a5 100644
--- a/Porting/release_schedule.pod
+++ b/Porting/release_schedule.pod
@@ -46,7 +46,7 @@ you should reset the version numbers to the next blead series.
   2014-09-20  5.21.4          Steve Hay
   2014-10-20  5.21.5          Abigail
   2014-11-20  5.21.6          Chris "BinGOs" Williams
-  2014-12-20  5.21.7          ?
+  2014-12-20  5.21.7          Max Maischein
   2015-01-20  5.21.8          Matthew Horsfall
   2015-02-20  5.21.9          ?
   2015-03-20  5.21.10         ?
diff --git a/pod/perlpolicy.pod b/pod/perlpolicy.pod
index 7f7befa..4dbf5ad 100644
--- a/pod/perlpolicy.pod
+++ b/pod/perlpolicy.pod
@@ -204,6 +204,14 @@ do our best to smooth the transition path for users of 
experimental
 features, you should contact the perl5-porters mailinglist if you find
 an experimental feature useful and want to help shape its future.
 
+Experimental features must be experimental in two stable releases before being
+marked non-experimental.  Experimental features will only have their
+experimental status revoked when they no longer have any design-changing bugs
+open against them and when they have remained unchanged in behavior for the
+entire length of a development cycle.  In other words, a feature present in
+v5.20.0 may be marked no longer experimental in v5.22.0 if and only if its
+behavior is unchanged throughout all of v5.21.
+
 =item deprecated
 
 If something in the Perl core is marked as B<deprecated>, we may remove it

--
Perl5 Master Repository

Reply via email to