On Mon, Mar 21, 2011 at 10:10 PM, Jesse Vincent <je...@bestpractical.com> wrote: > > I'm in the process of compiling and linking the list of issues that > block the release of Perl 5.14.0.
The version of ExtUtils::MakeMaker we claim to be shipping in blead is 6.57_05. There are six changes in blead since 6.57_05 was integrated (3 by me, 2 by Reini, and 1 by Dave M.). See: <http://perl5.git.perl.org/perl.git/history/HEAD:/cpan/ExtUtils-MakeMaker> I *think* all these changes are in upstream at <https://github.com/Perl-Toolchain-Gang/ExtUtils-MakeMaker> but aren't in anything released yet. 6.57_06 has been on CPAN since October but all of these changes are since then, so I think what will happen if someone installs 5.14.0 and then upgrades EU::MM from CPAN is that they'll lose these six changes and get a different set of changes. So do we want to release 5.14.0 with an "experimental" version of EU::MM? And if we do, shouldn't we make it a *real* experimental release rather than an illegitimate child of an experimental release? And there are also quite a few changes upstream that don't appear to exist in a release yet, even an experimental one. Are any of them release-worthy? Yes, we've been bad about bumping version numbers when we had to patch something in blead. But, frankly, I'm afraid to try that because you have to touch about 30 files and if you don't do it perfectly the MakeMaker test suite takes revenge. Plus there's no way to know what to bump it to since you might be taking a number that will also be taken by the next, divergent, CPAN release. So it's really not practical to bump the version outside of the MakeMaker release process. But since MakeMaker is used to build the core, it's also not always practical to wait for a MakeMaker release to do things that need doing in core. I apologize for merely waving a red flag without volunteering to do anything, but I'm a bit overwhelmed by a pile of actual bugs that need fixing.
