--From http://rakudo.org/parrot/index.cgi?bug_day_2007_06_16--
Bug Day
On Saturday, 16 June 2007, please join us on IRC in #parrot
(irc.perl.org) to work on closing out as many RT
(https://rt.perl.org/rt3/) tickets as possible in the parrot queue. This
will help us get ready for the next
-- From http://rakudo.org/parrot/index.cgi?bug_day_2007_04_14 --
Bug Day
On Saturday, 14 April 2007, please join us on IRC in #parrot
(irc.perl.org) to work on closing out as many RT
(https://rt.perl.org/rt3/ ) tickets as possible in the parrot queue.
This will help us get ready for the next
--From http://rakudo.org/parrot/index.cgi?bug_day_2007_03_17--
Bug Day
On Saturday, 17 March 2007, please join us on IRC in #parrot
(irc.perl.org) to work on closing out as many RT (https://rt.perl.org/
rt3/) tickets as possible in the parrot queue. This will help us get
ready for the next
Fellow birders~
On Saturday, 13 January, 2007, please join us on IRC in #parrot
(irc.perl.org) to work on closing out as many RT
(https://rt.perl.org/rt3/) tickets as possible in the parrot queue.
This will help us get ready for the next release of parrot 0.4.8,
scheduled for Tuesday 16 January 2
I took the liberty of creating
http://rakudo.org/parrot/index.cgi?bug_day_december_dec_16_2006
and pointing to it from the main site and the front page of the wiki.
It would probably be a good idea to add more details here. I added a few
various TODOs, but am not tied to them.
We alr
We have too many bugs. We could use more programmers and testers and
documenters.
and some examples need to update, for example, replace deprecated syntax with
new, etc. For newcomer, examples is good start point to learn, but
only if it's up to date.
We have too many bugs. We could use more programmers and testers and
documenters.
We need a bug day!
By rough consensus, we'll gather virtually on the 16th in #parrot on
irc.perl.org to walk through the bug database, closing all resolved or
invalid tickets, verifying what we can v
