Front page | perl.perl5.porters |
Postings from April 2012
tl;dr: Search ahead for "XXX" Here is a link to the meta-ticket for 5.16.0 blockers: https://rt.perl.org/rt3/Ticket/Display.html?id=94978 You don't need to bother clicking, though. I'll summarize: there's only one blocker on it. It's about UTF-8 (especially ":utf8") being stupid, and it's: https://rt.perl.org/rt3/Ticket/Display.html?id=100058 We have a number of patches that will be getting applied soon to deal with problems in this area, and that will close the last blocker. There are also a few "can we get this applied before 5.16?" bugfixes in flight, although very few, and I think we should see the end of them this week, unless something very nasty is turned up. Also, we're on the lookout for bugs introduced in the last round of bugfixes for the previous round of bugfixes. (We call it a code freeze, but there seems to be a decent amount of motion still going on!) I'd also like to close a few more of the Pod::Html tickets at... https://rt.perl.org/rt3/Ticket/Display.html?id=112014 ...but I'm not promising anything just yet. My hope is to see Pod::Html dual-lifed in one for or another shortly after 5.16.0 so that bugfixes won't have to wait for 2013 to be generally applicable. More urgently, the perl5160delta needs to be finished. My plan there is to complete a 3rd and 4th pass over it, bringing in some sections intentionally omitted during its initial compilation. Then I'll be asking for a general review of the document, especially one or two sections. So, where does this all leave us? Here's what I see happening next: * the last blocker is closed * one or two minor remaining fixes get in through very convincing argument * some bugs are identified in recent bugfixes and fixed very conservatively * the code freeze grows even colder * perl5160delta is lovingly kicked around * perl-5.16.0-RC1 ### My guess is that RC1 is due in about two weeks. Maybe a little less, ### maybe a little more. A virtually identical tarball, without the RCx ### marker will be released when we've had a release candidate go at least a ### week without any "showstopper" class bugs. This means we may get 5.16.0 before 5/16/2012. I am not going to be too broken up by the loss of a little gag like that. ;) Finally: please note that I've been reviewing my p5p folder over and over for the past few days, looking for unresolved questions and other things that got left hanging. If you think that I am ignoring some question you sent me, please just remind me. I'm not ignoring anything on purpose. -- rjbsThread Next