Branch: refs/heads/book/rmg-improvements
Home: https://github.com/Perl/perl5
Commit: 8636ec79459c03f44224fb33464886bd7ef4c300
https://github.com/Perl/perl5/commit/8636ec79459c03f44224fb33464886bd7ef4c300
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: 07ca42ef174909ed7a75b85bacccebc13bea19e9
https://github.com/Perl/perl5/commit/07ca42ef174909ed7a75b85bacccebc13bea19e9
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
- 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/b28277bbe47e...07ca42ef1749
To unsubscribe from these emails, change your notification settings at
https://github.com/Perl/perl5/settings/notifications
