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 keeping up
   with all the new tickets on trac is very time consuming, and
   possibly the problem was filed in the wrong category.

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 tickets and see if
   they were fixed in a recent release
   (perhaps this won't be such a problem once the duplicates are
   filtered properly)

I know some people already spend time doing some of this, but it's
impossible to fight with more than 2000 open tickets without an
organized effort.


Most linux distributions already use a similar approach. The issues are
first assigned to the bug-wrangler team, where the email address points
to a mailing list. Then someone takes the new ticket, and follows up
until the right developer gives feedback.

This would also be an easy way to consolidate duplicate tickets, even
if they are filed in different components. The members of the
bug-wrangler mailing list will be able to see the initial report for
every ticket, so they might recall a similar problem reported a few
days ago.

Another advantage is that the members of this team don't need to be
developers, or even know how to code. It is enough to be able to listen
to user requests and use trac.

This could also be a good starting point for people who want to get
into Sage development, since it provides an opportunity to look through
the library and become familiar with the internal structure of Sage.


Comments?


Cheers,
Burcin

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Reply via email to