[Python-Dev] New bugtracker project

Aahz aahz@pythoncraft.com
Wed, 22 May 2002 14:21:14 -0400

On Wed, May 22, 2002, David Ascher wrote:
> As someone said, he's referring to the SF concepts.  In Mozilla land, 
> bugzilla is used for everything from bug management, patch management 
> (it is the repository on which people indicate who'se reviewed what 
> patch, when it was checked in, etc.), mailing-list-proxy and random 
> banter (e.g. the "give hyatt $50" bug), user feedback mechanism (via bug 
> voting, which AFAICT doesn't "work") as well as general project 
> management.  I think it's a lousy tool for project management, but then 
> again I think all the tools I've seen are lousy tools for project 
> management =).
> It is a feature that bugzilla is corruptible that way, one which would 
> be good to have in the new system.  The key low-level feature which 
> enables this is keywords and a peer-enforced policy rather than 
> rule-based policy (as in "_please_ don't change milestones if you're not 
> part of the PDT team" or such).

Well, no, I don't agree with that last part.  I'm all in favor of
rolling all possible project tracking features into a single tool, but
that doesn't mean one wants all features available to every user, and it
especially doesn't mean that one wants all features available to every
user for any specific subset of system records.

For example, I think it's highly appropriate that if we use this system
for actual project management that project goals assigned to a specific
release get "locked" to everyone but Guido after Guido has approved
assignment of that goal to that release.  I think preventing stupid
mistakes is an eminently reasonable use of the system.

Which reminds me of another feature request:

* CVS-like system rollbacks to defined states (minimum) or archiving of
every change (preferred).
Aahz (aahz@pythoncraft.com)           <*>         http://www.pythoncraft.com/

"In the end, outside of spy agencies, people are far too trusting and
willing to help."  --Ira Winkler