% mdiep has left mdiep!~mdiep@v-adsl-fh-178-170.umnet.umich.edu
% mdiep has joined #parrotsketch
% rdice has joined #parrotsketch
% jhorwitz has joined #parrotsketch
% kj has joined #parrotsketch
% particl1 has joined #parrotsketch
% particle has left particle!~particle@c-24-19-3-148.hsd1.mn.comcast.net
% particl1 is now known as particle
% allison has joined #parrotsketch
% chromatic has joined #parrotsketch
<chromatic> Roll call!
* allison here
* spinclad (peanut gallery)
<jhorwitz> aqui
<kj> i'm here. and have a report from francois
<kj> who's not here.
<chromatic> Alright, let's begin then.  allison?
<allison> - I spent time at Frozen Perl and on the flight hacking on the PMC parser bug, and resolved it.
<allison> - I've started the mass conversion in the existing PMCs.
% Coke has joined #parrotsketch
<allison> (there's room for others to pitch in on that)
<allison> - I also spent time with jhorwitz at Frozen Perl, looking over some of the mod_language* and embedding stuff.
<allison> - Looks like the embedding PDD is nearly ready to launch.
<allison> EOR
<chromatic> I fixed several bugs.
<chromatic> As far as I know, all tests pass now on Linux PPC and x86 (32-bit).  I think Darwin's clean too.
<chromatic> I also closed several tickets, and hope to get a few more done.
<chromatic> next?
<jhorwitz> i guess that's me....
<jhorwitz> mod_perl6 talk at frozen perl went very well
<jhorwitz> finished ModPerl6::Registry, with compiled script caching and per-script namespaces.  uses string IO layer for stdout redirection, as we don't have a proper tie-like interface for IO handles.
<jhorwitz> had a good chat w/ allison about embedding docs (actually the POD, not the PDD).
<jhorwitz> began exporting Parrot_* functions that should be part of the public API and adding some missing prototypes
<jhorwitz> EOR
<chromatic> Coke?
<Coke> yup:
<Coke> Mostly coding standards updates; cleaned some warnings; nothing user-visbile.
% davidfetter has joined #parrotsketch
<chromatic> francois?
<Coke> Sadly, EOR.
% kj is now known as fperrad
<fperrad> Lua: update the standard libraries (follow Lua 5.1.3)
<fperrad> Lua: waiting for Bug #49328 (it's a prerequisite for others GC problems)
<fperrad> Lua: shift to PCT not yet planned (currently no spare time available)
<fperrad> FYI: SF parrot-win32, only 70 downloads for the latest monthly release
<fperrad> EOR
% fperrad is now known as kj
<kj> I only added some function documentation.
<kj> .eor
<chromatic> particle?
<particle> ~ some c89 and headerizer fixups
<particle> ~ it's time to internationalize parrot! so i'm working on a gettext config step. it works locally, will apply soon
<particle> ~ some rakudo updates, including more of the pod grammar
<particle> ~ i'd like to help with pdd17pmc branch, but i'm currently getting a gc bug while running perl6grammar, haven't tracked it down yet
<particle> .end
<chromatic> tewk?
<chromatic> Anyone I missed?
<chromatic> Alright, let's move to question time.  I have two.
<particle> release tomorrow. NEWS and PLATFORMS updates are most welcome.
<chromatic> First, are there any potential committers we should consider?
<particle> core? i can't think of any. but tene has been active on a few hlls.
<particle> i'm sure his hll hacking would be easier with a commit bit
<chromatic> Makes sense to me.  Anyone have any concerns?
<allison> sounds good to me
<jhorwitz> none here
<kj> sounds like cardinal has a new maintainer :-)
<chromatic> Alright, who wants to give him the contributor agreement and tell him to fax/mail it to me?
<particle> i'll take care of the details and mentor him.
<chromatic> Other questions?
<allison> particle: Can you post the details on the gc bug you're getting in the pdd17pmc branch? (Or, if you already did, point me to the ticket or mailing-list thread.)
<particle> allison: roger, wilco. starting debugger now.
<allison> thanks
<Coke> chromatic: FYI, I'm getting some errors on darwin; will make sure a ticket is opened shortly.
<chromatic> Okay, that reminds me of my second question.
<chromatic> kid51 and Coke and I spent some time tracking down Darwin seggies.  It's much, much easier when we can blame a specific patch.
<Coke> ... I don't like where this is going. =-)
<chromatic> It would be great to track when test failures started to occur.  Jim did a binary search of a few hundred commits to find one error, and I'd like to keep that under 10.
<chromatic> Of course, we have to keep the tests usually passing for this to work. Apparently there have been known failures on Darwin for a while....
<allison> sounds like the continuous smokes idea again
<chromatic> That would be great, but I think we can handle this without recruiting more smoke boxes.
<allison> it's easy enough for those of us developing on darwin to test before we commit, the problem seems to be that lots of people don't have darwin to test on
<allison> what's your idea?
<chromatic> Ask for binary searches as follow-up material in failure reports.
<particle> allison: see #50996
<allison> hmmm... I'd tend to put the binary search on the plate of the person doing the debugging
<chromatic> Kinda hard for me to do a binary search on Darwin at the mo'.
<Coke> allison: except that the person doing the debugging may not have that platform.
<chromatic> If we *know* that Darwin's all green as of r25870 (for example), then it's much easier to track a failure to a patch somewhere between here and r25880.
<chromatic> I'd just like us to be able to narrow things down more easily.
<allison> chromatic: you have access to two Darwin laptops sitting in the next room
<chromatic> True, but I meant Darwin x86.
<Coke> I think for developers, that's fine; Having joe bug reporter do that will be more of a pain; and the better the smoke frequency, the easier that'll be to narrow down even with our current smoke-fra-structure.
<allison> for jim or me, it's easy enough to do a binary search, but not all bug reporters will have that ability
<chromatic> Anyway, the point is that sometimes we can fix bugs just by reading the code of commits.
<allison> coke: yes
<particle> who do we know with smolder experience and tuits?
<particle> it'd be nice to convert to smolder.
<allison> particle: agreed
<chromatic> That sounds good to me.
<allison> Steve Peters was going to work on getting smoulder to use TAP
* particle gives stevep a biscuit
<allison> particle: thanks for the ticket, I'll dig into it
<chromatic> Okay, any other questions?
<chromatic> Any blockers (except Francois's GC/Lua bug that confuses me)?
<allison> jhorwitz: is it docs/embed.pod you were working on?
<jhorwitz> yes
<Coke> chromatic: the ascii_compare segfault.
<allison> jhorwitz: okay, it is nearly launchable as the PDD, so I'll merge the two.
<chromatic> Coke, any chance you can reduce that to a very simple PIR example?
<jhorwitz> allison: sounds good to me
<Coke> chromatic: I'll try.
* particle wonders what deadlines are coming up next
<allison> I'm working on the security PDD now
<particle> allison: how are you doing with the recent milestones?
<allison> and the concurrency dev milestone is the end of this month
<Coke> I haven't been following up on that. bad coke. 
<Coke> (I need updates from allison, jonathan & patrick.) (mostly jonathan & patrick)
<allison> chromatic/particle: do you have some time this week to work on updating PMCs?
<chromatic> Certainly can.
<allison> There are two good examples in r25832 and r25862.
<particle> can do.
<chromatic> Is there anything else?
<Coke> not here.
<chromatic> Let's adjourn to #parrot then, and help Patrick finish tomorrow's release.
<allison> thanks all!
% allison has left #parrotsketch
% Coke has left #parrotsketch
% kj has left #parrotsketch
% chromatic has left #parrotsketch
% jhorwitz has left #parrotsketch
% davidfetter has left #parrotsketch
% rdice has left rdice!~richard_d@CPE0014bfafbbd5-CM0011e6ecf48a.cpe.net.cable.rogers.com
% rdice has joined #parrotsketch
% rdice has left rdice!~richarddi@CPE001217e365c7-CM00159a01d44c.cpe.net.cable.rogers.com
% particle has left particle!~particle@c-24-19-3-148.hsd1.mn.comcast.net
% particle has joined #parrotsketch