Branch: refs/heads/blead
Home: https://github.com/Perl/perl5
Commit: 1a5f6e546448508977651abf75b6994870bc136e
https://github.com/Perl/perl5/commit/1a5f6e546448508977651abf75b6994870bc136e
Author: Philippe Bruhat (BooK) <[email protected]>
Date: 2026-06-03 (Wed, 03 Jun 2026)
Changed paths:
M Porting/make-rmg-checklist
M Porting/release_managers_guide.pod
Log Message:
-----------
add 5.NEXT placeholder to the RMG
Co-authored-by: Eric Herman <[email protected]>
Commit: cd281db9e81a2696f5424c5688cbf33c22b5f758
https://github.com/Perl/perl5/commit/cd281db9e81a2696f5424c5688cbf33c22b5f758
Author: Philippe Bruhat (BooK) <[email protected]>
Date: 2026-06-03 (Wed, 03 Jun 2026)
Changed paths:
M Porting/release_managers_guide.pod
Log Message:
-----------
clarify the different cases of "bump the version number"
The version number must be bump in separate occasions:
- when releasing a BLEAD-FINAL (or anything besides a BLEAD-POINT),
bump the version at the beginning of the release process
- after releasing a BLEAD-POINT, bump the version to prepare for
the next dev release (even it the next release is likely to be
an RC or BLEAD-FINAL)
- after releasing a BLEAD-FINAL, bump the version to the new .0
for the new dev cycle
Commit: 04ac2edde8bd88a72f6d3ebbd973529d194ccf5d
https://github.com/Perl/perl5/commit/04ac2edde8bd88a72f6d3ebbd973529d194ccf5d
Author: Philippe Bruhat (BooK) <[email protected]>
Date: 2026-06-03 (Wed, 03 Jun 2026)
Changed paths:
M Porting/release_managers_guide.pod
Log Message:
-----------
RMG: separate email preparation from version bump
- make the perlpolicy update more prominent by adding a specific section
header
- clarify the PERL_API constants instructions and make them release-specific
- move the end-of-support email instructions to the email section
Co-authored-by: Eric Herman <[email protected]>
Compare: https://github.com/Perl/perl5/compare/97fa0bdf58e8...04ac2edde8bd
To unsubscribe from these emails, change your notification settings at
https://github.com/Perl/perl5/settings/notifications
