Hey All, Something to talk about further at tomorrow's Boulder Ruby Group meeting: A local Rails Bugmash in Boulder during the May 7-8 weekend. Thinking of having it as a two afternoon thing - 1pm to 5pm/6pm on both days of the weekend; rubyists getting together during Mother's day wknd in the afternoons and squishing some bugs in rails source code....
Here are some instructions I got from Aaron Patterson of the Rails Core team: *I'll try to outline the best things people can do. People should not feel required to finish all steps, and I tried to order the steps by experience. So, new people should be able to do at least the first step, and experienced people should be able to do all of them. But even if the less experienced people to just one of the steps, it will help the more experienced people out. For tickets that have no patches attached: 1. If the person hasn't provided enough information to reproduce, comment and ask for more info. 2. Try to reproduce the problem. Comment on the ticket with your results, including detailed steps for repro. 3. Write a test to demonstrate the problem and attach that as a patch 4. Write a fix for the problem to go along with the test, attach that as a patch 5. If it seems like it should be fixed in 3-0-stable, try backporting and attach the backport commit as well For tickets that have a patch: 1. Check to see if the patch still applies cleanly. Comment on the ticket with whether or not the patch applies. 2. If the patch does not apply cleanly, treat the ticket as if it had no patch (follow the above steps) 3. Make sure the patch has a test. If it has no test, either write one, or comment that it needs a test 4. If the patch applies and has tests, try to run the rails tests. Comment with the results of your test run. For either type of ticket, if you make it through all the steps, just assign the ticket to me and I'll apply the patches. You should be able to treat pull requests with a similar process. If I have time that weekend, I will try to participate. I hope that helps! * -- Cheers, Prakash N Murthy (347) 228 3993 http://twitter.com/_prakash
_______________________________________________ Bdrg-members mailing list Bdrg-members@rubyforge.org http://rubyforge.org/mailman/listinfo/bdrg-members
