Branch: refs/heads/book/rmg-improvements
Home: https://github.com/Perl/perl5
Commit: c2657b4572d52b1629022e43cf3cc166179fd429
https://github.com/Perl/perl5/commit/c2657b4572d52b1629022e43cf3cc166179fd429
Author: Philippe Bruhat (BooK) <[email protected]>
Date: 2026-05-20 (Wed, 20 May 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: cb12f95a02526bac628c70574e4f048a783c512d
https://github.com/Perl/perl5/commit/cb12f95a02526bac628c70574e4f048a783c512d
Author: Philippe Bruhat (BooK) <[email protected]>
Date: 2026-05-20 (Wed, 20 May 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: b28277bbe47e7327648d2dfd1ec554088b91c73f
https://github.com/Perl/perl5/commit/b28277bbe47e7327648d2dfd1ec554088b91c73f
Author: Philippe Bruhat (BooK) <[email protected]>
Date: 2026-05-20 (Wed, 20 May 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
- generate release-specific end-of-support note instructions
Co-authored-by: Eric Herman <[email protected]>
Compare: https://github.com/Perl/perl5/compare/7dddf9675e17...b28277bbe47e
To unsubscribe from these emails, change your notification settings at
https://github.com/Perl/perl5/settings/notifications
