youcef92 / flotr

Automatically exported from code.google.com/p/flotr
0 stars 0 forks source link

Wild growth in ticket tracker #130

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
There are a *lot* of tickets here, many of which about issues that have
been resolved.  It would be helpful to close those, and if some points are
still outstanding perhaps create a new ticket which is more specifically
about that point. 

There are also some tickets of which the status is unclear.

All this would also make it easier for constributers to help out fixing bugs.

Tickets that need some consideration:
7, 21, 22, 29 (not really an issue?), 48, 54(?), 80 (unresolved?), 70
(status unknown), 99, 96 (if > 2 axis is not supported or planned, there's
no point to keep the ticket open), 91 (desperate for feedback), 88, 111
(desperate for feedback), 108, 107, 126 (duplicate of 70), 

Original issue reported on code.google.com by peter....@solide-ict.nl on 7 Jun 2010 at 11:25

GoogleCodeExporter commented 8 years ago
I know, there are a lot of pending issues :( 
Would you like me to give you permissions to manage a little bit the tracker ?

Original comment by fabien.menager on 21 Jun 2010 at 9:49

GoogleCodeExporter commented 8 years ago
Sure, I could close some tickets that are obviously finished. However, the ones 
that require some feedback should probably be handled by yourself.

Original comment by peter....@solide-ict.nl on 22 Jun 2010 at 7:26

GoogleCodeExporter commented 8 years ago
OK, I've marked those issues that were in my list and obviously done. The 
remaining ones need some feedback.  I'll try to go over the list once more at a 
later time to see if I missed any.

Original comment by peter....@solide-ict.nl on 22 Jun 2010 at 1:30

GoogleCodeExporter commented 8 years ago
I've gone over the list again and made a few patches and commented on a few 
tickets. It should be a little bit more manageable now.

We should take care not to let the list grow much bigger again. We can make 
sure by going over the tickets that are real bugs and fixing them, and just 
closing those where the status is unsure or vague and they haven't responded on 
requests for clarification.

Original comment by peter....@solide-ict.nl on 21 Jul 2010 at 12:09