summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJames E Keenan <jkeenan@cpan.org>2018-06-25 20:23:19 -0400
committerSteve Hay <steve.m.hay@googlemail.com>2018-11-02 23:12:56 +0000
commitd2696631951ad8cf6802173c8bd079ebf9d0e436 (patch)
treeefc44e6d80988441c002a918a2c099635fb7bfba
parent692bf97a5911fe6f1261651d797abc866c52e7e0 (diff)
downloadperl-d2696631951ad8cf6802173c8bd079ebf9d0e436.tar.gz
Correct release schedule for 5.29/5.30.
Signed-off-by: Abigail <abigail@abigail.be> (cherry picked from commit ecdd443b6ac63aef56110bdff4133a1afec7abba)
-rw-r--r--Porting/release_schedule.pod22
1 files changed, 18 insertions, 4 deletions
diff --git a/Porting/release_schedule.pod b/Porting/release_schedule.pod
index 2c5427bcf7..5007e015cb 100644
--- a/Porting/release_schedule.pod
+++ b/Porting/release_schedule.pod
@@ -15,11 +15,11 @@ deemed necessary by the Pumpking.
Code freezes (which happen in the 5.29.X series)
- 2018-03-20 5.27.7 Contentious changes freeze
- 2018-04-20 5.27.8 User-visible changes to correctly
+ 2019-02-20 5.29.8 Contentious changes freeze
+ 2019-03-20 5.29.9 User-visible changes to correctly
functioning programs freeze
- 2018-05-20 5.27.9 Full code freeze
- 2018-06-20 5.28.0 Stable release!
+ 2019-04-20 5.29.10 Full code freeze
+ 2019-05-20 5.30.0 Stable release!
=head2 Perl 5.28
@@ -61,6 +61,20 @@ When shipping a release, you should include the schedule for (at least)
the next four releases. If a stable version of Perl is released,
you should reset the version numbers to the next blead series.
+=head2 Perl 5.29
+
+ 2018-06-?? 5.29.0 Sawyer X
+ 2018-07-20 5.29.1
+ 2018-08-20 5.29.2
+ 2018-09-20 5.29.3
+ 2018-10-20 5.29.4
+ 2018-11-20 5.29.5
+ 2018-12-20 5.29.6
+ 2019-01-20 5.29.7
+ 2019-02-20 5.29.8
+ 2019-03-20 5.29.9
+ 2019-04-20 5.29.10
+
=head2 Perl 5.27
2017-05-31 5.27.0 ✓ Sawyer X