on Thu Nov 08 2007, "John Maddock" <john-AT-johnmaddock.co.uk> wrote:
David Abrahams wrote:
That means establishing a 1.36.0 milestone, declaring the criteria for including a ticket in 1.35.0, telling people that if they want an exception they have to get you to okay it, and maybe making any assignments of tickets to 1.35.0 and 1.36.0 that are obvious. Then we all have a list of issues to focus on killing off and we don't need to pester people as much.
If you would like me to take on some of these tasks, please ask me.
[dead silence since Monday]
Am I really the only one that thinks this matters? I realize that as a project we don't have a lot of experience with effective use of bug and task tracking, but we also haven't been all that effective in the run-up to a release. Using the tools we have effectively can make a big difference.
Violent agreement from here.
We should also triage all the "Yet to be determined" bug reports as well, is there a way to get a report of all the bugs Trac issues that haven't been at least *looked at* yet?
Yes. And that's another good reason to keep the 1.36.0 milestone separate from the "TBD" milestone. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com