"A.M. Kuchling" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> On Mon, Apr 24, 2006 at 09:45:41PM -0700, Neal Norwitz wrote:
>> hard bugs to fix. I guess there are also a lot that we can't
>> reproduce and the submitter is MIA. Those might be easier. Ping them
>> if not reproduc
"Alan McIntyre" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> I suppose the "new code" emphasis may make writing a proposal to fix
> bugs an exercise in futility. :)
I personally consider anything *you* write to be 'new code'. Let us see
what Google thinks. Patches that other
On Tue, 25 Apr 2006, A.M. Kuchling wrote:
> On Mon, Apr 24, 2006 at 09:45:41PM -0700, Neal Norwitz wrote:
>> hard bugs to fix. I guess there are also a lot that we can't
>> reproduce and the submitter is MIA. Those might be easier. Ping them
>> if not reproducible, if no response in a month, we
A.M. Kuchling wrote:
> On Mon, Apr 24, 2006 at 12:30:12PM -0400, Alan McIntyre wrote:
>
>> My unglamorous proposal is to review bugs & patches (starting with the
>> oldest) and resolve at least 200 of them. Is that too much? Too few?
>>
> I'd suggest 75 or maybe 100 bugs or patches, not
Terry Reedy wrote:
>> My unglamorous proposal is to review bugs & patches (starting with the
>> oldest) and resolve at least 200 of them.
> Funny, and nice!, that you should propose this. I thought of adding
> something like this to the Python wiki as something I might mentor, but
> hesitate
On Mon, Apr 24, 2006 at 09:45:41PM -0700, Neal Norwitz wrote:
> hard bugs to fix. I guess there are also a lot that we can't
> reproduce and the submitter is MIA. Those might be easier. Ping them
> if not reproducible, if no response in a month, we close.
The last time there was a thread sugges
On 4/24/06, A.M. Kuchling <[EMAIL PROTECTED]> wrote:
> On Mon, Apr 24, 2006 at 12:30:12PM -0400, Alan McIntyre wrote:
> > My unglamorous proposal is to review bugs & patches (starting with the
> > oldest) and resolve at least 200 of them. Is that too much? Too few?
> > I'll fix as many as possibl
"Alan McIntyre" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hi all,
>
> I would like to participate in the Summer of Code as a student. At the
> moment it looks like the Python tracker on SF has about 2100 open bugs
> and patches, going back to late 2000.
The latest weekly tra
On Mon, Apr 24, 2006 at 12:30:12PM -0400, Alan McIntyre wrote:
> My unglamorous proposal is to review bugs & patches (starting with the
> oldest) and resolve at least 200 of them. Is that too much? Too few?
> I'll fix as many as possible during the SoC time frame, but I wanted to
> set a realist
Hi all,
I would like to participate in the Summer of Code as a student. At the
moment it looks like the Python tracker on SF has about 2100 open bugs
and patches, going back to late 2000. I'm assuming that a fair number
of these are no longer be applicable, have been fixed/implemented
already, e
10 matches
Mail list logo
