% rdice has joined #parrotsketch
% rdice has left rdice!~richarddi@CPE001217e365c7-CM00159a01d44c.cpe.net.cable.rogers.com
% rdice has joined #parrotsketch
% rdice has left rdice!~richard_d@CPE0014bfafbbd5-CM0011e6ecf48a.cpe.net.cable.rogers.com
<spinclad> yesterday's sketch, now that Tweety's back:
% spinclad is now known as |
<|> 13:57:49 < Coke> hoping so. allison?
<|> 13:58:10 < particle> 's all good.
<|> 13:58:16 < allison> what features are on the list to mark the 0.6.0 release?
<|> 13:58:37 < particle> there's a wiki page for that...
<|> 13:58:42 < allison> IIRC, particle had a wiki page
<|> 13:58:49 < allison> link?
<|> 13:59:27 < particle> http://www.perlfoundation.org/parrot/index.cgi?release_planning
<|> 14:00:36 < Coke> I think we might want to rejigger some of those; are there any that can be crossed off today?
<|> 14:00:47 < allison> Okay, so Feb is 0.6.0
<|> 14:01:10 -!- jhorwitz_ [~chatzilla@pool-68-236-46-96.phil.east.verizon.net] has joined #parrotsketch
<|> 14:01:18 < allison> actually, Jan could be 0.6.0, but could use another review of exceptions PDD to make sure we covered 
<|>                     everything
<|> 14:02:00 < particle> yes, i'd like you and patrick to talk about exceptions
<|> 14:02:07 < particle> i know he has questions
<|> 14:02:07 < Coke> works for me.
<|> 14:02:19 < Coke> (I think we have an old timer committer lined up for february)
<|> 14:02:43 < allison> particle: aye, I know there are a couple of features that didn't get implemented yet
<|> 14:03:02 < allison> okay, sounds like Feb is a good month for 0.6.0
<|> 14:03:23 < allison> that answers my question
<|> 14:04:00 < Coke> Note to anyone reading this: 0.9 is probably not going to be the last point release. =-)
<|> 14:04:30 < allison> coke: that's 0.99
<|> 14:04:48 < Coke> I've an email from the sponsors who are happy with the forward progress. Yay.
<|> 14:05:00 < Coke> Anyone got anything else?
<|> 14:05:22 < Coke> going once?
<|> 14:06:10 -!- jhorwitz [~chatzilla@pool-68-236-46-96.phil.east.verizon.net] has quit [Ping timeout: 360 seconds]
<|> 14:06:19 -!- jhorwitz_ is now known as jhorwitz
<|> 14:06:53 < Coke> All right, I'm calling it. Thanks to everyone for their hard work. Any committers who read this but 
<|>                  aren't here, feel free to join us next week.
<|> 14:07:34 < allison> thanks coke!
% | is now known as spinclad
<spinclad> oops
<spinclad> wrong pastebuffer; let's try that again:
% spinclad is now known as |
<|> 09:01:51 < pmichaud> I may end up missing #parrotsketch today -- will send along a report if I get a chance
<|> 09:37:51 -!- rdice [~richard_d@CPE0014bfafbbd5-CM0011e6ecf48a.cpe.net.cable.rogers.com] has joined #parrotsketch
<|> 09:50:43 -!- amoore [~amoore@65.165.109.82] has joined #parrotsketch
<|> 10:24:20 < Tene> No Tweety, eh?  So this is unlogged?  >.>
<|> 13:21:01 -!- jhorwitz [~chatzilla@pool-68-236-46-96.phil.east.verizon.net] has joined #parrotsketch
<|> 13:25:41 -!- chromatic [~chromatic@sub17-30.member.dsl-only.net] has joined #parrotsketch
<|> 13:26:13 -!- barney [~bernhard@p549A23C5.dip0.t-ipconnect.de] has joined #parrotsketch
<|> 13:29:27 -!- allison [~chatzilla@dsl-241-77-141.telkomadsl.co.za] has joined #parrotsketch
<|> 13:29:44 -!- Coke [~coke@cpe-72-228-52-192.nycap.res.rr.com] has joined #parrotsketch
<|> 13:30:16 < chromatic> Good $?LOLCALTIME
<|> 13:30:34 < Coke> OH HAI WE CAN HAZ PARROTSKETCH?
<|> 13:31:01 < chromatic> KTHX
<|> 13:31:09 < allison> HAI COKE
<|> 13:31:21 < Coke> I see we've all been infected with lolcode.
<|> 13:31:44 < allison> viral
<|> 13:32:01 < Coke> let's be all crazy and go non-alpha. Tene?
<|> 13:32:15 -!- tcoppi [~thisnukes@208.72.153.109] has joined #parrotsketch
<|> 13:32:35 < Coke> (only because I know you submitted at least one patch this week. =-)
<|> 13:33:01 < Coke> too slow. jhorwitz?
<|> 13:33:09 < particle> Tweety--
<|> 13:33:23 < Coke> ah. good catch. someone able to log this for later playback?
<|> 13:33:29 < jhorwitz> started looking at embed.pod and comparing to my embedding notes from mod_parrot
<|> 13:33:51 < jhorwitz> put shiny new mod_parrot docs on the perlfoundation wiki
<|> 13:34:05 < Tene> Aw, too slow by one minute!  I was lecturing!
<|> 13:34:09 < Tene> I'm logging.
<|> 13:34:26 < jhorwitz> found some segfaults when Parrot_new() multiple times and submitted a test
<|> 13:34:32 < jhorwitz> EOR
<|> 13:34:45 < jhorwitz> s/when/when calling/
<|> 13:35:11 < Coke> jhorwitz: danke. Tene, danke: anything to report?
<|> 13:36:47 < Tene> Fixes for NQP Aggregate handling.  I think that was this week.
<|> 13:37:06 < Tene> Working on spec-compliant expression handling for lolcode.
<|> 13:37:13 < Tene> EOR
<|> 13:37:17 < Coke> danke.
<|> 13:37:23 < Coke> chromatic?
<|> 13:37:39 < chromatic> That's not even ASCIIbetical.
<|> 13:37:52 < chromatic> I worked on some PMC PDD changes on the branch, mostly .pmc parsing and emitting.
<|> 13:38:07 < chromatic> I profiled some code that helped pmichaud speed up PGE notably.
<|> 13:38:13 < chromatic> I applied some patches.
<|> 13:38:28 < chromatic> I hope to poke at the Lua segfault in the next couple of days, besides doing whatever Allison needs on the PMC branch.
<|> 13:38:29 < chromatic> that's it
<|> 13:39:17 < Coke> danke. my report:
<|> 13:39:18 < Coke> - Been working on a "web 2.0" read only front end for RT to help guide
<|> 13:39:18 < Coke> people looking for things to work on.
<|> 13:39:18 < Coke> - started languages/lolcode, which seems to have drawn some interest, patches, and some non-parrot blog entries.
<|> 13:39:25 < Coke> EOR
<|> 13:39:48 < Coke> particle? (if you're still about?)
<|> 13:39:54 < particle> ~ started journaling at use.perl to give folks more info on my commits for pct and perl6
<|> 13:39:55 < particle> ~ added -h and -v support for pct::hllcompiler and perl6
<|> 13:39:55 < particle> ~ working on -c and -e support
<|> 13:40:01 < particle> ~ made some problems with pbc_to_exe and windows, then fixed them
<|> 13:40:01 < particle> ~ small patches to lolcode
<|> 13:40:01 < particle> ~ committed a new tool (tools/dev/nopaste.pl) to paste files or stdin to nopaste.snit.ch -- plus applied enhancements by limbic_region++
<|> 13:40:01 < particle> .end
<|> 13:40:36 < Coke> Spif. Patrick?
<|> 13:40:58 < particle> no show, no report.
<|> 13:41:08 < Coke> barney?
<|> 13:41:16 < barney> Worked on Eclectus.
<|> 13:41:16 < barney> Started to use PAST in Scheme-XML as intermediate representation.
<|> 13:41:23 < barney> .eor
<|> 13:41:44 < Coke> Ok. pinged most of everyone else privately, no response, leaving allison!
<|> 13:41:54 < allison> - The first part of the week I spent implementing more of the concurrency scheduler, to smooth some of the joints between the new event system and the old threading model.
<|> 13:42:02 < allison> - I resolved most of the failures, and marked 3 tests as TODO for next month, when I'll be revamping threading/STM anyway.
<|> 13:42:11 < allison> - The second part of the week I've been working on PDD 17 implementation.
<|> 13:42:24 < allison> - Work going rapidly, thanks to some perl -pie magic.
<|> 13:42:33 < chromatic> mmm, pie
<|> 13:42:46 < allison> - Most of the work involved is code cleanups.
<|> 13:43:06 < allison> - My thanks to chromatic for the tasks he's been completing.
<|> 13:43:08 < allison> EOR
<|> 13:43:21 < Coke> Anyone else have anything to report? Questions to queue?
<|> 13:43:36 < Coke> I have been having fun; hopefully everyone else is too.
<|> 13:43:40  * allison HAZ QUESTION
<|> 13:43:48 < Coke> go ahead. =-)
<|> 13:44:02 < particle> i've got a q, too
<|> 13:44:16 < allison> I've gone back to doing primary development in a branch.
<|> 13:44:26 < allison> The main problem with working in a branch is losing language testing. Working in trunk I know the active language developers will let me know if I break anything. In a branch, I just don't know if I'm breaking things.
<|> 13:44:48 < particle> all you can do is languages-test
<|> 13:45:00 < allison> How far are we from making language tests a reliable judge of what should be passing?
<|> 13:45:09 < particle> that's up to the hll devs
<|> 13:45:13 < allison> can we todo everything we expect to fail?
<|> 13:45:19 < particle> hrmm
<|> 13:45:29 < Coke> I think there are two issues here.
<|> 13:45:32 < allison> drop languages that aren't actively maintained from the main languages-test target?
<|> 13:45:39 < Coke> 1) we can't test everything in languages-test
<|> 13:45:48 < particle> how about using a benchmark, rather than forcing hll devs to todo everything failing?
<|> 13:46:03 < Coke> 2) not every language in languages-test passes 100% (due to cruft, or maintenance, or ...)
<|> 13:46:05 < allison> I'd be okay with making a special target
<|> 13:46:17 < allison> languages-for-dev-test
<|> 13:46:18 < Coke> I think we can resolve 2 by todo'ing things that fail.
<|> 13:46:34 < particle> some languages may not support todo
<|> 13:46:36 < Coke> 1 requires someone to finish up the unified-testing todo.
<|> 13:47:02 < allison> I just need a way of knowing that I didn't break something in languages that will bite the language devs when I merge the branch back in
<|> 13:47:33 < Coke> allison: your best bet is communication; warn the list of impending re-merge, encourage language developers to double check their language in your branch.
<|> 13:47:33 < particle> allison: best way right now is probably to take output of languages-test at your branch point and save it to disk
<|> 13:47:33 < chromatic> ... and easier to debug than saying "Language devs, check out the branch before we merge and see if any of this pile of changes broke your stuff."
<|> 13:47:42 < particle> that is, make a baseline of languages-test output
<|> 13:47:54 < particle> then compare that baseline to current output of languages-test
<|> 13:47:56 < allison> coke: we tried that with objects, and it was still pretty traumatic
<|> 13:48:04 < Coke> tcl still hasn't recovered. =-)
<|> 13:48:05 < particle> questions can go to hll devs
<|> 13:48:07 < allison> coke: that's why I didn't use a branch for events
<|> 13:48:41 < allison> coke: but as the events implementation showed, there are rough patches to doing major development in trunk too
<|> 13:48:57 < Coke> I think as long as we're responsive when things do accidentally get broke, we'll be ok.
<|> 13:49:08 < particle> we don't have the smoke infrastructure we need.
<|> 13:49:12 < allison> I really hate having 2 weeks of work on my harddrive not committed anywhere, and trunk-based dev is difficult for collaboration
<|> 13:49:14 < particle> this is just more proof.
<|> 13:49:27 < Coke> (better smoke system)++
<|> 13:49:36 < allison> I'm all for that.
<|> 13:49:54 < Coke> We have some time before 0.5.2; when do you think you'll be ready with core (not hll) stuff from your branch?
<|> 13:50:04 < Coke> if we have a week or so before the cut, I think we'll be ok.
<|> 13:50:27 < allison> I plan to roll it in right after the release, just for general sanity
<|> 13:50:34 < Coke> after? ah. no worries then.
<|> 13:50:46 < allison> yup, no worries is the best way
<|> 13:51:03 < allison> I can send out a message to the list a week before merging
<|> 13:51:12 < Coke> In the meantime, ISTR that kid51 setup a page on the wiki describing the current/desired smoke situation. We should probably all take a pass at that and add our 2cents.
<|> 13:52:11 < allison> sounds good
<|> 13:52:19 < allison> KTXHBYE
<|> 13:52:27 < allison> I mean EOQ
<|> 13:52:48 < Coke> k. particle?
<|> 13:52:57 < particle> ok, so who's doing the release? has the person been notified? are we on track? bugday? etc.
<|> 13:53:24 < chromatic> Andy wants to announce the bugday, but no one has answered his questions yet.
<|> 13:53:27 < Coke> Bob Rogers is the guy. Sent him an email today to double check on his status.
<|> 13:53:45 < Coke> if anyone wants to volunteer to be on channel during the day saturday, I'm sure Bob won't mind.
<|> 13:53:58 < Coke> I can devote some time, but it's a crapshoot as to when.
<|> 13:54:14 < chromatic> I can be on in the AMish.
<|> 13:54:20 < allison> I'll be around, on a European timezone
<|> 13:55:15  * allison queues another question
<|> 13:55:17 < Coke> that sounds like a reasonable amount of coverage... anyone want to whip up a note to Andy (cc'ing bob?)
<|> 13:55:21 < barney> I might be around for som hours
<|> 13:56:37 < Coke> Ok. I'll get Andy the information he needs.
<|> 13:56:56 < Tene> I'll probably be around during a lot of Saturday.
<|> 13:56:59 < Coke> If Bob has issues cutting the release, I'll troll for another volunteer.
<|> 13:57:11 < Coke> but for now, I'm assuming on track. That cover you, particle?
<|> 13:57:49 < Coke> hoping so. allison?
<|> 13:58:10 < particle> 's all good.
<|> 13:58:16 < allison> what features are on the list to mark the 0.6.0 release?
<|> 13:58:37 < particle> there's a wiki page for that...
<|> 13:58:42 < allison> IIRC, particle had a wiki page
<|> 13:58:49 < allison> link?
<|> 13:59:27 < particle> http://www.perlfoundation.org/parrot/index.cgi?release_planning
<|> 14:00:36 < Coke> I think we might want to rejigger some of those; are there any that can be crossed off today?
<|> 14:00:47 < allison> Okay, so Feb is 0.6.0
<|> 14:01:10 -!- jhorwitz_ [~chatzilla@pool-68-236-46-96.phil.east.verizon.net] has joined #parrotsketch
<|> 14:01:18 < allison> actually, Jan could be 0.6.0, but could use another review of exceptions PDD to make sure we covered everything
<|> 14:02:00 < particle> yes, i'd like you and patrick to talk about exceptions
<|> 14:02:07 < particle> i know he has questions
<|> 14:02:07 < Coke> works for me.
<|> 14:02:19 < Coke> (I think we have an old timer committer lined up for february)
<|> 14:02:43 < allison> particle: aye, I know there are a couple of features that didn't get implemented yet
<|> 14:03:02 < allison> okay, sounds like Feb is a good month for 0.6.0
<|> 14:03:23 < allison> that answers my question
<|> 14:04:00 < Coke> Note to anyone reading this: 0.9 is probably not going to be the last point release. =-)
<|> 14:04:30 < allison> coke: that's 0.99
<|> 14:04:48 < Coke> I've an email from the sponsors who are happy with the forward progress. Yay.
<|> 14:05:00 < Coke> Anyone got anything else?
<|> 14:05:22 < Coke> going once?
<|> 14:06:10 -!- jhorwitz [~chatzilla@pool-68-236-46-96.phil.east.verizon.net] has quit [Ping timeout: 360 seconds]
<|> 14:06:19 -!- jhorwitz_ is now known as jhorwitz
<|> 14:06:53 < Coke> All right, I'm calling it. Thanks to everyone for their hard work. Any committers who read this but aren't here, feel free to join us next week.
<|> 14:07:34 < allison> thanks coke!
% | is now known as spinclad
% integral has left integral!bsmith@adsl-212-20-244-147.lumison.co.uk
% pmichaud has left pmichaud!pmichaud@feather.perl6.nl
% leo has left leo!lt@feather.perl6.nl
% PerlJam has left PerlJam!duff@feather.perl6.nl
% pmichaud has joined #parrotsketch
% integral has joined #parrotsketch
% leo has joined #parrotsketch
% PerlJam has joined #parrotsketch
% leo has left leo!lt@feather.perl6.nl
% PerlJam has left PerlJam!duff@feather.perl6.nl
% integral has left integral!bsmith@adsl-212-20-244-147.lumison.co.uk
% pmichaud has left pmichaud!pmichaud@feather.perl6.nl
% pmichaud has joined #parrotsketch
% integral has joined #parrotsketch
% leo has joined #parrotsketch
% PerlJam has joined #parrotsketch
% rdice has joined #parrotsketch
% pmichaud has left pmichaud!pmichaud@feather.perl6.nl
% rdice has left rdice!~richard_d@CPE0014bfafbbd5-CM0011e6ecf48a.cpe.net.cable.rogers.com
% rdice has joined #parrotsketch
% rdice has left rdice!~richard_d@CPE0014bfafbbd5-CM0011e6ecf48a.cpe.net.cable.rogers.com