[IronPython] Bug Weekend prior to 2.7
dvdotsenko at gmail.com
Thu Feb 3 23:56:42 CET 2011
Is there a analyse on how one can participate in bug sprint?
Wouldn't want to go over same bugs others already reviewed. Do we mark each
bug with "yep, still a problem" comment? Do we make a list and post it
somewhere on shared Google docs spreadsheet?
On Feb 3, 2011 12:52 PM, "Dino Viehland" <dinov at microsoft.com> wrote:
> Me too
> From: users-bounces at lists.ironpython.com [mailto:
users-bounces at lists.ironpython.com] On Behalf Of Richard Nienaber
> Sent: Thursday, February 03, 2011 12:11 PM
> To: Discussion of IronPython
> Subject: Re: [IronPython] Bug Weekend prior to 2.7
>> Anyone else willing and able to participate?
> I reckon I could find a couple of hours to help out. Count me in.
> On Thu, Feb 3, 2011 at 7:35 PM, Jeff Hardy <jdhardy at gmail.com<mailto:
jdhardy at gmail.com>> wrote:
> I'd like to organize a bug weekend prior to the release of 2.7, to try
> and get some low-hanging fruit dealt with. For those not familiar with
> the idea, a couple of days are set aside and as many people as
> possible go through the issue tracker verifying bugs and creating
> patches and test cases, and getting those patches into the tree. Also,
> you don't have to dedicate your whole weekend; the idea is to get more
> people as possible involved by giving them an easy way to get their
> feet wet. I would rather see lots of people spend a couple of hours
> than a couple of people spend the whole weekend.
> There is no release scheduled (http://bit.ly/gJx2zI) for the weekend
> of Feb. 12, which would make it ideal to get bugs into RC1. I should
> be mostly free that weekend to help out. Anyone else willing and able
> to participate?
> - Jeff
> Users mailing list
> Users at lists.ironpython.com<mailto:Users at lists.ironpython.com>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ironpython-users