In perl.git, the branch blead has been updated

<http://perl5.git.perl.org/perl.git/commitdiff/cf217b12874de6af9cdcd4724a3264a76a18b6d3?hp=3db23aeceed93497d1456928f0d3561a32f74a02>

- Log -----------------------------------------------------------------
commit cf217b12874de6af9cdcd4724a3264a76a18b6d3
Author: Abigail <[email protected]>
Date:   Sat Jul 19 18:36:11 2014 +0200

    Tick off the 5.20.0 and 5.20.1 releases.

M       Porting/release_schedule.pod

commit 53e6b8f769d9ca5cc081dcdb870bb0caf1f547d3
Author: Abigail <[email protected]>
Date:   Sat Jul 19 18:34:08 2014 +0200

    "all question marks" is ambigious.
    
    Because if just a single question mark is used, it means the release
    manager is unknown. Only if multiple question marks are used it
    means it isn't known whether this release will happen.

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

Summary of changes:
 Porting/release_schedule.pod | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Porting/release_schedule.pod b/Porting/release_schedule.pod
index b8fa9b6..18f8fd3 100644
--- a/Porting/release_schedule.pod
+++ b/Porting/release_schedule.pod
@@ -8,7 +8,7 @@ release_schedule - Perl 5 release schedule
 
 This schedule lists the projected or historical development and
 release schedules for the next, current and previous stable versions
-of Perl.  Dates with all question marks will only be releases if
+of Perl.  Dates with two or more question marks will only be releases if
 deemed necessary by the Pumpking.
 
 =head2 Perl 5.20
@@ -41,8 +41,8 @@ you should reset the version numbers to the next blead series.
 
 =head2 Perl 5.21
 
-  2014-05-20  5.21.0          Ricardo Signes
-  2014-06-20  5.21.1          Matthew Horsfall
+  2014-05-20  5.21.0 ✓        Ricardo Signes
+  2014-06-20  5.21.1 ✓        Matthew Horsfall
   2014-07-20  5.21.2          Abigail
   2014-08-20  5.21.3          Peter Martini
   2014-09-20  5.21.4          Steve Hay

--
Perl5 Master Repository

Reply via email to