[MacRuby-devel] bug smash recap

[Eloy Duran]

Idem dito. Thanks a lot everyone! I had tons of fun :)

On 6 dec 2010, at 20:48, Matt Aimonetti wrote:

> Thanks to everyone who joined the fun, we went from around 230 unscreeened tickets to 32: http://www.macruby.org/trac/report/19
> We now have 80 open tickets scheduled for 1.0 http://www.macruby.org/trac/report/17
> 
> The provided help saved the team an incredible amount of work.
> 
> What's next? My guess is that we are going to leave the bot and the channel around since it seems to provide a very nice workflow (Thanks Eloy for setting it up) but I'll let Laurent address what he wants to do next.
> 
> - Matt
> 
> 
> On Fri, Dec 3, 2010 at 1:55 PM, Laurent Sansonetti <lsansonetti at apple.com> wrote:
> A short recap regarding tomorrow's bug smash!
> 
> The bug smash will happen Saturday 4th on IRC, network freenode (the main server seems to be chat.freenode.net), channel #macruby.
> 
> The goal of this event is to triage all the bugs into 2 categories: for 1.0 and for Later. Then, making sure all the 1.0 bugs have proper reductions attached. It's going to be a boring job but it needs to be done.
> 
> If you have any question regarding MacRuby's development or internals, feel free to also stop by and ask it there. We may not yet have a list of easy bugs to give to new hackers, but we can still answer questions and give pointers to the source code. We assume that after triaging all the bugs, we will have a good list of bugs we can give to new hackers, in further bug smash events.
> 
> As we found out yesterday, it's impossible to sync up for a long time people living in US, Europe and Japan :) I will be online tonight and tomorrow from noon to midnight (US west coast time). Other contributors have different schedules but I think there should always be someone in the channel.
> 
> Here is the workflow I have in mind for bug triaging. Instead of adding a new field to trac, I was thinking of re-using the milestone field. I just added 2 new milestones: "MacRuby 1.0" and "MacRuby Later". I propose that we set the milestone of each ticket to either one of those. Once a ticket is set to the "MacRuby 1.0" milestone, we can hack on it. Once it's fixed in trunk, we can move the milestone to the upcoming MacRuby one (such as "MacRuby 0.8", currently), then close it.
> 
> When a bug is properly reduced to a simple test case (if applicable), the #reduction keyword can be attached to the ticket.
> 
> As an example, let's say we have this ticket we want to get fixed for 1.0. We set the milestone to "MacRuby 1.0". A few days later, someone comes up with a good bug reduction, he attaches it to the ticket and the #reduction keyword. A few days later, someone finds a good fix, he commits it to trunk, then set the milestone to "MacRuby 0.8" then close the ticket.
> 
> Thoughts?
> 
> Laurent
> 
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> 
> 
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20101206/c397f936/attachment.html>