Thanks for taking this project on Jorge! I think it will be a huge help.
One small amemdment to your plan would make me very happy. I would like to have 2.x created in addition to 2.1, because I want us to start thinking seriously about what goes into 2.1 in February, and that's just next week. 2.x should be the place for feature requests that are not specifically approved for 2.0 or 2.1. Does that work for you? On Sat, Jan 24, 2009 at 1:31 PM, percious <[email protected]> wrote: > > +1 on this. Sooner the better, esp. the upgrades of modules. > > On Jan 24, 11:16 am, Jorge Vargas <[email protected]> wrote: >> Hello guys >> >> I'm currently very unhappy with the state of our trac we have 207, a >> ton of them are over a year old and many are just invalid. Specially >> all the stuff in __unclassified__ >> >> So I think desperate times call for desperate measures. I think we >> should cut the ticket count at least by half when this is done. This >> is my current set of goals, I'll sit down and do it sometime this week. >> >> 1- Close as won't fix, all tickets related to unmaintained code, >> catwalk, with a reference to use Rum or Catwalk2 >> fastdata -> sprox >> admi18n -> babel >> ModelDesigner, we have nothing for this. Not sure what to do about them >> toolbox -> respective external component >> >> 2- half maintained code. bugfixes will stay open, feature request will >> be closed with reference >> - TGwidgets -> ToscaWidgets >> - kid -> genshi >> - identity -> repoze.what >> >> 3- regarding tg itself. >> >> I'll create two more milestones called 1.x and 2.x therefore we'll have >> >> 1.0.x bugfix - bug fixes for 1.0 >> 2.0b* , as many as we may need >> 2.0 everything that mark approves as a goal for 2.0 >> 2.x (rename 2.1) everything that is 2.x but not approved into 2.0 (aka >> tg2+ future, even tg3 stuff) >> 1.1 everything florent approves to go there >> 1.1b* (rename 1.1 beta 3, cosmetic change) >> 1.1 maintenance (rename 1.1.x bugfix, for consistency) >> 1.5 everything approved to go into 1.5 >> 1.x everything else still 1.x specific >> >> __future__ and __unclassified__ deleted, all those tickets will go to >> one of the above. >> >> This will helphttp://trac.turbogears.org/roadmaplook cleaner. >> >> 4- anything that doesn't makes sense or is very very old (#12 is still >> open) or someone asked for more feedback and it never got back, will be >> closed >> >> 5- If you have/own an old ticket that fits into one of the above >> categories and for some reason you will want to leave it out, pleae >> make a comment ON the ticket not here. > > > -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
