% rdice has joined #parrotsketch
% barney has joined #parrotsketch
% kjs has joined #parrotsketch
% Coke has joined #parrotsketch
<Coke> I vote we wait until chromatic & allison show up, DST confusion non-withstanding.
<barney> k
<Coke> Ok. The hour extension is over...
<Coke> I am back from a week of vacation; looking forward to just helping get 0.5.0 out the door; I think most of the heavy lifting is already done.
<Coke> anyone blocking on anything or looking for something to do, feel free to ping me via email or #parrot.
<Coke> barney?
<Coke> integral?
% allison has joined #parrotsketch
<barney> More refactoring of languages/scheme
<integral> Coke: I'm just listening.
<barney> Starting on Eclectus. A Scheme->PBC compiler, implemented in Scheme
<barney> .eor
<Coke> sounds nifty. Allison, you're up.
<allison> - Working on Concurrency PDD
<allison> I'll be traveling the next day or so, but will check it in on the other side.
<allison> EOR
<Coke> kjs?
<kjs> I fixed pirc/macro, now all macro invocations get a unique id, meaning that labels and locals declared with .label and .macro_local respectively are truely unique
<kjs> I got a bit confused in the syntax in macros, I think it needs another review.
<kjs> .end
<Coke> PerlJam?
* allison has a q for question time
<Coke> noted.
<Coke> pmichaud?
<pmichaud> I had a longish chat with obra last week regarding the current state of perl6 compiler and various other compiler tools.
<pmichaud> I'm writing this up as STATUS and ROADMAP documents to be checked into the repo.
<pmichaud> I'm about a week behind on coding changes, and I know I'm delayed on the AST implementation deadline.  It's my current task.
<pmichaud> Only blocking on available time/energy at the moment, but that seems to be resolving itself now.
<pmichaud> eor
<Coke> /^[r-t]/i ?
<Coke>  /^[r-t]/i ?
<spinclad> ENOREPORT  # one q though
<Coke> Ok. pending any more reports, quick Q/A... allison?
<allison> kjs: could you briefly outline the confusion in the macro syntax in an email? the PDD may just not be clear
<kjs> ok. will do, it's not a big deal, but it just needs to be thought over well, so that users are not scared away by strange and inconsistent syntax.
<allison> aye, consistency is important
<allison> you made a comment about .label being used for locals?
<kjs> no .label is used for declaring unique labels
<kjs> .macro_local for unique locals
<allison> ah, rereading your note "labels and locals declared with .label and .macro_local respectively "
<kjs> I didn't touch IMCC again for these updates
<kjs> it's too scary
<allison> I got as far as "labels and locals declared with .label"
<kjs> right, respectively is the keyword here :)
* pmichaud queues one quick comment/q
<allison> ok, so we'll have to tackle IMCC at some point
<allison> EOQ
<Coke> spinclad, q?
<spinclad> i'll cede my q turn to pmichaud if i may
<Coke> k
<spinclad> (requeuing after)
<Coke> pmichaud, q?
<pmichaud> The Test::TAP::Model module no longer seems to install on my system... thus I'm no longer able to run smoke tests.
<pmichaud> any thoughts about how to resolve it?  I don't want to eat too many cycles tracking it down myself.
<spinclad> could this relate to Test::Harness 3?
<Coke> A similar issue was reported on dragonfly over the long weekend.
<spinclad> it seems to demand some rejiggering
<Coke> I believe there is an effort to remove our dependency on that module.
<pmichaud> I have no idea.  All I know is that using "install Test::TAP::Model" from a cpan shell gives me errors.
<Coke> but I haven't seen an update on the mailing list. I will troll for one today and see if we can get this resolved before release.
<pmichaud> I didn't think it was quite appropriate for an RT ticket in parrot, but I can file one if that helps for tracking purposes
<Coke> I would not be against updating to TH3 for 0.5.0
<Coke> sure. "make smoke broken".
<pmichaud> it's not like I'm on a bizarre platform at the moment, though... kubuntu 7.10 on i386
<pmichaud> anyway, I'll file the ticket.  Thanks.
<barney> Shouldn't that be solved in the 'unified_testing' branch ?
<Coke> k. spinclad?
<Coke> barney: if it's solved, it should moved back to trunk. =-)
<pmichaud> perhaps it should be solved in the unified_testing branch, however it's currently broken in the trunk :-)
<pmichaud> and in many respects it's not parrot related at all -- this is simply a problem with the CPAN module itself
<Coke> still, it's affecting parrot, so we need a ticket to track it, even if our ticket just points to their ticket.
<Coke> so, "fix smoke before release"... spinclad, what was your Q?
<spinclad> q: i'm wondering about the release schedule:  pmichaud mentioned a weeks delay in his work, which seems to me important enough to be worth slipping for.
<Coke> A fair cop, and a good segway.
<spinclad> (sorry, was afk)
<Coke> I am ok with 0.5.0 slipping a week to accomodate pmichaud's work in this area. I am unsure of how this will affect grant issues on the parrot scale (not pmi's). allison, do you see a negative impact there?
<pmichaud> looking at this week, I'm not sure we'd need to slip.  I'll know better by Thursday morning, however.
<pmichaud> i.e., I think I can make up the week today/tonight/tomorrow.
<Coke> ... Ok. let's defer the question until then, and we'll see?
<Coke> I think thursday is a good go/no go date.
<allison> spinclad: we try to keep the releases low pressure
<Coke> right, but 0.5.0 is big. 0.5.1 we could ship with a missing feature no problem. =-)
<pmichaud> I'll report to Coke and the list one way or the other by Thursday 18:30 UTC
<allison> so, we wouldn't delay the release, just delay the new feature to next realease
<allison> 0.5.0 is objects
<spinclad> i'd be happy with 'release when ready', but i'm not voting
<allison> AST can wait until 0.5.1
<Coke> I have no problem making a call on thursday regardless. but unless anyone hears otherwise, we're a go for tuesday. =-)
<pmichaud> agreed
<allison> yup
<allison> coke: related, do you have a list of issues/important tickets for 0.5.0 release?
<Coke> I would love to see a round of cleanup in time for the release next week, improved testing coverage as well. bugfixen are always welcome; a nd the rt queue could use a shakedown.
<Coke> allison: I do not. the previous attempts to create such a list failed, so I haven't been pushing it.
<allison> how about a bug squashing saturday?
<Coke> as per usual.
<kjs> I sent some emails about some old tickets; only a few, but nevertheless. No answers yet on them.
<Coke> kjs: danke.
<kjs> geen dank
<kjs> mmm I wonder if I cc'd the list btw...
<Coke> Ok. I think that's a wrap, then; see folks on Saturday for bug day if nothing else.
<pmichaud> sounds great
<Coke> Thanks for all your work going into this release, everyone!
% allison has left allison!~chatzilla@sub17-30.member.dsl-only.net
% allison has joined #parrotsketch
% allison has left allison!~chatzilla@c-67-170-177-178.hsd1.or.comcast.net
% Coke has left #parrotsketch
% kjs has left #parrotsketch
% barney has left barney!~bernhard@p549A31B1.dip0.t-ipconnect.de
% rdice has left rdice!~richard_d@CPE0014bfafbbd5-CM0011e6ecf48a.cpe.net.cable.rogers.com
% pmichaud has left #parrotsketch
% rdice has joined #parrotsketch
% rdice has left rdice!~richarddi@CPE001217e365c7-CM00159a01d44c.cpe.net.cable.rogers.com