On Tue, Feb 22, 2011 at 2:05 AM, Julien Phalip <jpha...@gmail.com> wrote: > Hello, > > I was wondering if others would find it useful to introduce a new > field in Trac to characterise the nature of a ticket, allowing to > choose from at least: "bug report", "feature request", or > "optimisation". I think this would help bring the right focus during > alpha and beta stages, and also help people looking for tickets when, > for example, they're in the mood for fixing bugs. I believe the > Keywords field has been used in an ad hoc way for this before, but it > feels that something more structured would be more helpful.
Back in the dim, dark past, we actually *did* have a 'feature' flag. The problem we had was data integrity. Experience showed that reporters were very bad at differentiating between a "bug" and a"feature". The most common mode of failure was people reporting "Django, can't do X -- this is a bug", and then trying to convince them that lack of features isn't a bug. So, we removed the feature flag. Oh, the good old days :-) However, I agree that this is worth revisiting. Our community is now larger, we have more people to help with the Trac gardening, and there are less "obvious features" that are missing that could be misconstrued as a bug. Most importantly, since our process hinges on a "feature freeze", it is silly that we can't easily differentiate bugs from features in our issue tracker. There's another todo pending in Trac regarding the introduction of a 'needs feedback' state; we should probably roll the reintroduction of a feature flag into this. Russ %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
