Hi all,

in the process of the 1.1rc1 release and afterwards I went through all
of the tickets for TG 1 and those without a milestone and discarded many
cruft tickets:

- enhancements without patch or feedback in a long time
- enhancements for unmaintained (CatWalk) or to-be-phased-out (TG
widgets) components
- duplicates
- not reproducible with current version
- and some other misc tickets invalid for some reason or other

I also put all TG 1 tickets in one of the following milestones

- "1.0.x bugfix" for issues that should be fixed in one of the next TG
  1.0.x releases (and also in branches 1.1 and 1.5 of course)
- "1.0.x bugfix" for issues that should be fixed in one of the next TG
  1.1.x releases after 1.1. final (and also in the 1.5 branch)
- "1.1" for documentation issues that I still want to fix before 1.1 final
- "1.5" for issues particular to the 1.5 branch or to big for 1.1 point
releases (we may move back some to "1.1")

The idea behind this is to move incoming tickets into one of the "1.*.x
bugfix" or 1.5 milestones and then, when a new release is planned to
open a separate milestone for it (e.g. "1.0.9" or "1.1.1") and move the
tickets into them which are targeted for this release.

Currently there are no tickets for TG 1 with no milestone, but there are
about 30 tickets for TG2 with no milestone. Would it be possible to move
these into appropriate 2.x milestones, so it is more easy to see at one
glance for which branch a tickets is relevant? It would also make it a
lot easier to spot incoming tickets.

There are now 9 tickets for the 1.0.x bugfix milestone left open. Who is
willing to organize a 1.0.9 release for in about two or three weeks?


Chris

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to