I've set up a spreadsheet for keeping track of who's working on what bugs; it's at https://spreadsheets.google.com/ccc?key=0AlhyN5J6eVpldEFlcEhETjlRRnB0TnZ2RDNBLTMzdlE&hl=en. If you're working on a bug, *please* record it there so people don't duplicate effort.
If you want to write a patch and want something easy to start with, here are a couple of really easy ones: * http://ironpython.codeplex.com/workitem/27656 * http://ironpython.codeplex.com/workitem/29914 * http://ironpython.codeplex.com/workitem/29928 If you find another easy bug, add 'easy' to the Custom field. Figuring out which bugs are still valid and which aren't is a big part of this weekend, so bugs that are missing reproduction steps or test cases should have them added. If a bug has a patch or test case, add 'hastest' or 'haspatch' to the Custom field. - Jeff On Fri, Feb 11, 2011 at 12:53 AM, Jeff Hardy <[email protected]> wrote: > This is just a firendly reminder that the first IronPython Bug Weekend > is this weekend, February 12-13. You can find more information at > http://ironpython.codeplex.com/wikipage?title=first%20IronPython%20Bug%20Weekend. > > Remember, you don't have to dedicate the whole weekend - even finding > a couple of hours to write a patch will help out a lot! > > - Jeff > _______________________________________________ Users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
