Facundo Batista schrieb:
> 2007/11/23, Christian Heimes <[EMAIL PROTECTED]>:
>
>> Well, I'm exaggerating a bit but you probably get my point. The core
>> developers can't keep up with new bugs and check old bugs at the same
>> time. The resources are already stretched thin. But Brett gave me an
>
2007/11/23, Christian Heimes <[EMAIL PROTECTED]>:
> Well, I'm exaggerating a bit but you probably get my point. The core
> developers can't keep up with new bugs and check old bugs at the same
> time. The resources are already stretched thin. But Brett gave me an
One *fantastic* tool that exists
Facundo Batista schrieb:
>> won't need developer access to the svn. Instead their task is cleaning
>> up the tracker, categorizing bugs and checking patches. The tracker sure
>> contains a lot of outdated junk and already fixed bugs.
>
> One way to do this is to create a monthly (or each two mont
2007/11/23, Christian Heimes <[EMAIL PROTECTED]>:
> The Python bug tracker contains more than 1,300 bugs and it's growing.
> And growing ... and growing. I'm picking a bug once in a while or
> tossing some invalid bugs away but it's a helpless cause. The bugs are
> augmenting with anybody stopping
Christian Heimes schrieb:
> Dear fellow Python developers!
>
> The Python bug tracker contains more than 1,300 bugs and it's growing.
Not speaking of the 432 bugs that weren't migrated from SourceForge
(though I don't know how many of them were open).
> And growing ... and growing. I'm picking a
Dear fellow Python developers!
The Python bug tracker contains more than 1,300 bugs and it's growing.
And growing ... and growing. I'm picking a bug once in a while or
tossing some invalid bugs away but it's a helpless cause. The bugs are
augmenting with anybody stopping them.
Well, I'm exaggerat
