Front page | perl.perl5.porters |
Postings from April 2016
No blockers, let's ship it! Ha ha, it's April 1st, remember? Ugh. Anyway: PREVIOUS BLOCKER COUNT: 6 (but really 5 or maybe 4) CURRENT BLOCKER COUNT: 3 (plus HPUX/AIX??) ## blocking * BBC perl5i (but really: warnings for stat(@arr) https://rt.perl.org/Ticket/Display.html?id=126545 Tony has a smoke branch for adding a warning for stat(@arr). I hope we'll merge it RSN. Then we're done. * charset.t and subst.t on Solaris with use64bitall https://rt.perl.org/Ticket/Display.html?id=127746 I've asked Yves to have a look at this. Anybody else who wants to look, though, is welcome and encouraged! * Coredump in call_sv under threads https://rt.perl.org/Ticket/Display.html?id=127708 Maybe I'm misreading the discussion at http://www.nntp.perl.org/group/perl.perl5.porters/2016/03/msg235289.html but it sounds to me like: "We have two options on how to proceed. One is disruptive but correct. One is less disruptive but might not really be much of a fix." Are we better off, at this point, leaving it broken in v5.24, in a way consistent with the way it's broken in v5.22, so that we can only introduce new breakage in v5.26, with the benefit of really addressing the problem? That feels like my kind of answer. But maybe I misunderstand the discussion, as I said. ## not blocking * SIGFPE in S_make_trie https://rt.perl.org/Ticket/Display.html?id=126206 Not really blocking, just hoping for a comment or test, too. * memory leaks doing 'make test' https://rt.perl.org/Ticket/Display.html?id=127657 What we're hoping for, here, is some extra eyes. I'll remove this ticket from the blockers list (and maybe move it to v5.25.1 ticket) soon. But have a look anyway! -- rjbsThread Next