Skip to content

Conversation

book
Copy link
Contributor

@book book commented Oct 12, 2025

This covers almost all cases. The goal is that the release manager will only have the editing work left, and not have to spend time copy/pasting sections from the individual deltas into the final one.

Solves #23365.

  • This set of changes does not require a perldelta entry.

@book book marked this pull request as draft October 12, 2025 21:24
@book
Copy link
Contributor Author

book commented Oct 12, 2025

There is some work needed still:

  • the final version should be saved in pod/perldelta.pod
  • the Platform Support section is not handled yet

book added 18 commits October 12, 2025 23:27
For now this only supports the following sections:

* Core Enhancements
* Security
* Incompatible Changes
* Utility Changes
but die the next time we encounter them
in position_of_next_header, the search stops (and fails)
whenever a header of higher level is encountered
now we know it exists in both documents,
since we're processing the =head1 of the individual deltas
not just the first and last elements...
@book book force-pushed the book/merge-deltas branch from cbba49e to caf6318 Compare October 12, 2025 21:29
my $master = tree_for($template_file);

# loop over all the development deltas
for my $delta ( map tree_for($_), sort glob "pod/perl$tag_devel*delta.pod" ) {
Copy link
Contributor

Choose a reason for hiding this comment

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

A simple sort will put perl54310delta.pod before perl5432delta.pod.

Copy link
Contributor

Choose a reason for hiding this comment

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

Another argument for a new perldelta naming convention for perl 42 44

book and others added 6 commits October 14, 2025 00:12
Since the current perldelta has the latest changes,
and we want to keep them in order, we process the
deltas in reverse, and therefore inject the text at
the beginning of each section, instead of at the end.
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.

4 participants