kevin at dawson10
Apr 23, 2012, 5:10 AM
Post #13 of 21
On 17/04/12 21:48, Ricardo Signes wrote:
> tl;dr: Search ahead for "XXX"
> Here is a link to the meta-ticket for 5.16.0 blockers:
> 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:
> 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...
> ...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.
Just a reminder, about change log in perl5db.pl POD.
when i view perl5db.pl in perl 5.15.6
I expected to see change log for
as well as
perl 5.15.6 -> perl5db.pl v1.35
but it's missing
it only goes up to v1.33
5.14.2 => v1.33
5.15.0 => v1.34
5.15.1 => v1.34
5.15.2 => v1.34
5.15.3 => v1.34
5.15.4 => v1.34
5.15.5 => v1.34
5.15.6 => v1.35
5.15.7 => v1.35
5.15.8 => v1.35
5.15.9 => v1.35
* The "c [line num]" debugger command was broken by other debugger
changes released in 5.15.3. This is now fixed.
* Breakpoints were not properly restored after a debugger restart
using the "R" command. This was broken in 5.15.3. This is now fixed.
* The debugger prompt did not display the current line. This was
broken in 5.15.3. This is now fixed.