Skip to content

Several improvements to the RMG#24436

Open
book wants to merge 3 commits into
bleadfrom
book/rmg-improvements
Open

Several improvements to the RMG#24436
book wants to merge 3 commits into
bleadfrom
book/rmg-improvements

Conversation

@book
Copy link
Copy Markdown
Contributor

@book book commented May 20, 2026

Several improvements to the RMG:

  • move the end-of-support email instructions to the email section (Add EOL notices to the release announcement email template #24291)
  • make the perlpolicy update more prominent by adding a specific section header
  • filter out / duplicate slightly different versions of similar sections depending on the version being built (in particular "bump the version number")

(This set of changes does not require a perldelta entry.)

book and others added 3 commits May 20, 2026 18:08
Co-authored-by: Eric Herman <eric@freesa.org>
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
- 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 <eric@freesa.org>

=item C<5.NEXT>

The "next" perl version. Normally, this is just C<5.X.(Y+1)>, but if the
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to make sure I'm understanding this correctly, this is regarding what the version will be bumped to in blead; the reason for this exception is that after a stable 0 release, blead immediately becomes a development branch instead of continued for maintenance releases. Is that accurate to why this logic is here?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, exactly.

@book book requested a review from ap May 21, 2026 09:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants