As soon as the Perl release cycle enters a freeze, people start
committing their work in branches awaiting a merge. As blead gets
colder, hitting a full freeze, these start piling. Once 5.25.0 is out,
these are merged in, awaiting 5.25.1.
Since each development release is done once a month, and 5.25.0 was done
at the beginning of the month, it effectively means about a month and a
half for these to wait. Generally this would be fine, except it's the
first release past the freeze, meaning it's likely to collect a lot of
To accommodate this larger-than-usual set of changes, Matthew suggested
putting out 5.25.1 a bit earlier, on the 20th this month. I think that's
a good idea. What does that mean?
* On May 20th I will release 5.25.1, allowing all of these changes more
* Every release date stays the same, except it's the next version.
Instead of releasing 5.25.1 on June 20th, Matthew will release 5.25.2.
The stable release date stays the same as well.
* The states of freezing will all move one version forward. Instead of
"Contentious changes freeze" starting at 5.25.7, it will be start at
5.25.8. The full freeze will begin at 5.25.10 instead of 5.25.9.
If you have any objections, please let me/us know. Otherwise, 5.25.1
will be out in a week and a day on the 20th.
This is also a small reminder that blead is waiting for all your
commits. Bring it this week and you'll get longer smoking.