Branch: refs/heads/jkeenan/5-39-release-schedule-20230703
Home: https://github.com/Perl/perl5
Commit: 3ab47ea2c8efd070ebd0a2813b76c7b39f324018
https://github.com/Perl/perl5/commit/3ab47ea2c8efd070ebd0a2813b76c7b39f324018
Author: James E Keenan <jkee...@cpan.org>
Date: 2023-07-10 (Mon, 10 Jul 2023)
Changed paths:
M Porting/release_schedule.pod
Log Message:
-----------
Release schedule for 5.39 dev cycle
Skeleton only; no assignments yet.
NOTE: The 5.38.0 release manager opted not to do a "same day" or "next
day" of perl-5.39.0. Does that mean that we start this year's dev cycle
with a 5.39.0 release on July 20 --or a 5.39.1? (Assuming the latter.)
NOTE: As of the time of creation of this branch, having no 5.39.0
release we also lack a v5.39.0 annotated tag.
This has implications for CPANtesters reports. Task::CPAN::Reporter,
for example, by default does not transmit multiple PASS reports for a
given version of a given distro for a given Perl release. If I tested
WWW-Mechanize-2.17 against one of the perl-5.38.0-RC* releases, I can't
transmit a new report until we're at 5.39.*.
Commit: 892962ab2ffbb64123a3631c5f7375600b166e48
https://github.com/Perl/perl5/commit/892962ab2ffbb64123a3631c5f7375600b166e48
Author: James E Keenan <jkee...@cpan.org>
Date: 2023-07-10 (Mon, 10 Jul 2023)
Changed paths:
M Porting/release_schedule.pod
Log Message:
-----------
Reflect rjbs tag of aec03eb as v5.39.0
Compare: https://github.com/Perl/perl5/compare/90de5a0ba9f3...892962ab2ffb
