From: Victor B. <vb...@gm...> - 2007-09-17 05:00:24
|
> > The official bug tracker is now updated with the latest code, which > > includes the new tagging feature by jreese. I thought I would startup > > a discussion here relating to how we see tagging being used. In other > > words, brainstorm to provide some guidance to our users with regards > > to the usage of categories and tags. I can see users being a bit > > confused with entities like projects, sub-projects, categories, tags, > > and statuses. > > > > I'm interested to get your thoughts on this. The result of this > > discussion will probably end up on the wiki / blog. > > I think users should continue to try picking the category most > relevant to the bug they are reporting. Then, tags can be added to: > > 1. indicate one or more additional category. This is useful because > bugs could be not clearly assignable to only one category and/or a > proper category could be missing. > > 2. indicate the presence of a patch (useful until we have something > better in place) > So far we have the following tags: - patch: contains patch - soap api: related to SOAP API. - refactoring: code cleanup and refactoring I can see a need for ones like: - needsrepro: Need detailed "Steps to Reproduce". - needspatch: Acknowledge/confirmed but needs code contribution to implement. Ideas are welcome for other ones or better names for the ones suggested above. Regards, Victor |