![]() |
|
The stupid question is the question not asked | |
PerlMonks |
Re^2: 5.10 imminent?by grinder (Bishop) |
on Apr 12, 2007 at 14:54 UTC ( [id://609679]=note: print w/replies, xml ) | Need Help?? |
I [...] would like a code freeze for the purposes of producing a stable and well tested release now So does rgs, the current pumpking. There was a mammoth thread on p5p last month discussing some brokenness in pack, unpack and Unicode. At the end of it (if I got it straight) Rafael said that he didn't want to hold up 5.10 by fixing it now, because it would be too destabilising. 5.10 is in a freeze. He followed with a post asking for what open issues remained with blead. At the risk of repeating myself, if people want to see 5.10 released any time soon, the easiest way to help is to install a copy of blead (not 5.9.4, but rsync'ed from the public ActiveState repository) and draw up a list of every single module installed on your systems (perllocal will help with that). Then install CPAN::Reporter or CPANPLUS and start smoke testing them. If it fails on blead, but passes on 5.8.8, perlbug it. Get those errors out into the open. The more XS-ive, the more Unicodish, the more magical the module, the better. Acme modules push the parser and runtime in strange and peculiar ways. So do Damian Conway's. Smoke 'em all. And when all the lights on the control panel are green, we'll be ready for launch. Back to the original question: no, 5.9.4 was not a release candidate, but 5.9.5 will be. The plan, assuming sufficient energy and tuits from the volunteers who develop the core, is for 5.9.5 to be "it", with a few Release Candidates following on to smooth down any remaining rough edges. And then we have 5.10.0. • another intruder with the mooring in the heart of the Perl
In Section
Seekers of Perl Wisdom
|
|