% particle has left particle!~particle@c-24-22-165-145.hsd1.mn.comcast.net % particle has joined #parrotsketch % particle has left particle!~particle@c-24-22-165-145.hsd1.wa.comcast.net % particle has joined #parrotsketch % barney has joined #parrotsketch % chromatic has joined #parrotsketch % jhorwitz has joined #parrotsketch % jisom has joined #parrotsketch % mdiep has joined #parrotsketch Let's give everyone a couple of extra minutes. hi-o % allison has joined #parrotsketch Now that there are people ahead of me, ASCII-betically, let's start. I guess that's me. - I launched the PMC PDD. * particle bets allison didn't pre-type - Continued working on the object model. Particularly, running PGE and TGE on the new metamodel exposed several pieces that weren't fully implemented yet: running inherited parent's init vtable overrides. - Dedicated time every day to work with questions on the mailing list. EOR % Coke has joined #parrotsketch Tidied 'languages/scheme'. Applied some patches. .eor I fixed a couple of bugs, including a nasty one in OrderedHash. That let me get one of the HLL fixes in. Unfortunately, I couldn't get anywhere with the Darwin/x86/Tcl trifecta of EEEEVIL because gdb crashes in the same way the Hindenberg didn't fly. I've also been talking to some people about Intel's TBB and concurrency. There may be more to report there soon. Coke? I'm still coasting, parrot wise; ptc has prompted me to revisit the docs situation (website vs. 'make html', etc.) reserve a comment. EOR. i guess i'm up next migrating mod_parrot to server side tests using Apache::Test much better coverage need a way to redirect parrot's Test::More output using the request_rec object -- i'll register a comment so we can discuss later. and i broke mod_perl6 horribly when refactoring some mod_parrot code. working on that the past two days EOR jisom? working on getting my p3 up and running to work on jit on it, which should also help me on amd64, and be able to fix some of the pesky complex number issues on freebsd/amd64 eor * mdiep has nothing to report particle? ~ talked to folks on #tbb last week, glad chromatic's now also involved ~ reviewing pdds for pmc and exceptions (pmc first) ~ continued reviewing commits, found some bugs and corrected ~ preparing for a release today in mdiep's absence with plenty of help from committers in #parrot ~ now have mod_parrot checked out on ubuntu, hoping to fix configure so it'll build on windows ~ fixed some warnings and bugs release issues: ~ http://perlsix.org/svn/parrot/revision/?rev=21324 -- "do not edit" comment was removed from imcparser.c, dirs gone from filename comments ~ some unexpected successes on various runcores and platforms, some failures on os/x .end spinclad? tewk? Okay. Question time. I'll go first before I forget. particle, r21324 removed comments I added by hand. It's in the proposed Makefile patch you commented on last week. chromatic: yes, i'd like to see that applied today Will do. then we need imcparser regenerated Other questions? Allison had one about FUNKYDOC. I'm writing up a reply to Andy in email, but happy to talk here if it's useful. it's always useful to talk about andy behind his back, even if this channel is logged :) % PerlJam has joined #parrotsketch btw here's a link to a blog post about tbb and parrot, based on my discussions with kevinf: http://softwareblogs.intel.com/2007/09/07/threading-building-blocks-and-parrot-initial-investigation/ How's the state of the release look today? seems like a good time to release, if those few minor nits are fixed Did we reclaim CGP? Mostly? i haven't run languages tests chromatic: I see you've been logging into my osx box, yay. gdb crashing, boo; Can you write up how you reproduce that, so I can see about filing a bug report with apple? but core parrot tests are passing everywhere * jisom hasn't tested cgp more but hasn't heard problems languages looks mostly ok under linux pmichaud sent me http://nopaste.snit.ch:8001/11139 about CGP. oh yeah.... oh, i'm seeing that too. just now what system fails? 64-bit x86 Linux I thought. 64 bit FreeBSD's fine :- Is there anything else we need to discuss? Is anyone blocking on anything but time? (and Tcl/gdb seggies) Btw, allison++ for having some dedicated parrot time. The project will definitely benefit from that. coke: thanks, and I'm really glad to have the time :) are we okay with releasing if there's a few failures on alternate runcores? yes. (me personally) me too I'm most concerned about default runcore. I think of the others as experimental. I've found and fixed real bugs by exploring failing tests in those runcores. Some of those bugs have *not* been in the runcores. particle: yes, it's a dev point release perfect. let's start the ball rolling, then Should we re-enable CGP or wait until after the release? How about a 'make testrand', test a random runcore ? heh we need a release name there's always the "pick a random species of parrot" name Parrot 0.4.1x "make testrand" Parrot 0.4.16 "Random Species" how about that famous parrot that just died? Parrot 0.4.16 "Robert Jordan" we've already named a release for alex, i think yeah, 0.3.0 was Alex doh! "A Farewell to Alex" sure seems fitting If I = V/R is no longer true, will we call that "A Farewell to Ohms"? * allison groans Looks like we can call this one a week. See you all next time. % jhorwitz has left #parrotsketch % chromatic has left #parrotsketch % barney has left barney!~bernhard@p549A4151.dip0.t-ipconnect.de % Coke has left #parrotsketch % jisom has left jisom!~jisom@74-134-230-123.dhcp.insightbb.com % allison has left allison!~chatzilla@63.105.17.30 % mdiep has left #parrotsketch % particle has left particle!~particle@c-24-22-165-145.hsd1.wa.comcast.net % particle has joined #parrotsketch