On Thu, Oct 21, 2010 at 6:03 AM, Burcin Erocal wrote:
> On Sun, 17 Oct 2010 15:56:41 +0100
> Martin Albrecht wrote:
>
>> > I was thinking of setting up trac to send a notice to a mailing list
>> > for each new issue. Then people interested in this effort can follow
>> > this list and help out. Is
On Sun, 17 Oct 2010 15:56:41 +0100
Martin Albrecht wrote:
> > I was thinking of setting up trac to send a notice to a mailing list
> > for each new issue. Then people interested in this effort can follow
> > this list and help out. Is this possible? Can someone familiar with
> > the trac set up c
On Sun, 17 Oct 2010 17:45:08 +0200
Jeroen Demeyer wrote:
> On 2010-10-16 14:21, Burcin Erocal wrote:
> > - look at newly submitted tickets, notify the related developers
> How are you going to figure out who the "related developers" are?
I'd say there is an unofficial list of people who care ab
On Sun, Oct 17, 2010 at 6:39 AM, Dr. David Kirkby
wrote:
> On 10/16/10 01:21 PM, Burcin Erocal wrote:
>>
>> Hi,
>>
>> Motivated by the call for the bug days, here is an idea to manage the
>> rapidly increasing number of "new" tickets on trac.
>
> It is well known in industry that the cost to fix b
On 10/17/2010 07:39:44 AM, Dr. David Kirkby wrote:
In a similar way I feel "bug fix only releases" would be useful,
where one concentrates on removing bugs, and not adding features.
That idea has however been very much disliked by many people.
I believe that there are many people, who are n
On 2010-10-16 14:21, Burcin Erocal wrote:
> - look at newly submitted tickets, notify the related developers
How are you going to figure out who the "related developers" are?
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
On Sun, 17 Oct 2010 16:03:29 +0100
Martin Albrecht wrote:
> > I prefer "squad" to "wrangler," so I suggest PestSquad or
> > TracNinja. :)
>
> > Does anybody else have suggestions for a name?
>
> "Since 2005 a crack commando unit of developers is blamed for bugs
> they didn't commit. ... If you
> I prefer "squad" to "wrangler," so I suggest PestSquad or TracNinja. :)
> Does anybody else have suggestions for a name?
"Since 2005 a crack commando unit of developers is blamed for bugs they didn't
commit. ... If you have a patch, if no-one else can help, and if you can e-
mail them, maybe y
> I was thinking of setting up trac to send a notice to a mailing list
> for each new issue. Then people interested in this effort can follow
> this list and help out. Is this possible? Can someone familiar with the
> trac set up comment?
> IMHO, distributing work day by day, or weekly is still pu
On 10/17/10 03:16 PM, Jan Groenewald wrote:
Hi
I believe any belief that having "bug hunt weeks" is a long term
solution is rather flawed. The issues should be tackled at an
earlier stage.
Despite not being a sufficient solution, are they not nonetheless
necessary? Or at least helpful?
regar
Hi Martin,
On Sun, 17 Oct 2010 12:42:26 +0100
Martin Albrecht wrote:
> > We might be able to overcome this with a "bug-wrangler" team, people
> > who volunteer to
> >
> > - look at newly submitted tickets, notify the related developers,
> > ask for examples and test cases if the report doesn't
Hi Minh,
On Sun, 17 Oct 2010 01:35:01 +1100
Minh Nguyen wrote:
> On Sat, Oct 16, 2010 at 11:21 PM, Burcin Erocal
> wrote:
> > We might be able to overcome this with a "bug-wrangler" team,
>
> I would have thought "weed-wrangler" or "pest-wrangler". You know,
> Sage and horticulture :-)
We sh
On 2010-10-17 16:16, Jan Groenewald wrote:
> Hi
>
>> I believe any belief that having "bug hunt weeks" is a long term
>> solution is rather flawed. The issues should be tackled at an
>> earlier stage.
>
> Despite not being a sufficient solution, are they not nonetheless
> necessary? Or at least h
Hi
> I believe any belief that having "bug hunt weeks" is a long term
> solution is rather flawed. The issues should be tackled at an
> earlier stage.
Despite not being a sufficient solution, are they not nonetheless
necessary? Or at least helpful?
regards,
Jan
--
.~.
/V\ Jan Groen
On 10/16/10 01:21 PM, Burcin Erocal wrote:
Hi,
Motivated by the call for the bug days, here is an idea to manage the
rapidly increasing number of "new" tickets on trac.
It is well known in industry that the cost to fix bugs increases rapidly as they
time to fix them is delayed. See for exampl
> We might be able to overcome this with a "bug-wrangler" team, people
> who volunteer to
>
> - look at newly submitted tickets, notify the related developers, ask
>for examples and test cases if the report doesn't provide them,
>etc.
>
> - every once in a while, go through the open tic
Hi Burcin,
On Sat, Oct 16, 2010 at 11:21 PM, Burcin Erocal wrote:
> We might be able to overcome this with a "bug-wrangler" team,
I would have thought "weed-wrangler" or "pest-wrangler". You know,
Sage and horticulture :-)
> people
> who volunteer to
>
> - look at newly submitted tickets, not
Hi,
Motivated by the call for the bug days, here is an idea to manage the
rapidly increasing number of "new" tickets on trac.
Many of the bugs on trac are
- duplicates,
- already fixed, which can be closed after adding a doctest or
- has not been seen by a developer who can fix it since kee
18 matches
Mail list logo
