On Wed, Mar 31, 2010 at 12:30 PM, Juha Tuomala <Juha.Tuomala@xxxxxx> wrote: > Because it's a database of release's bugs, not a todo list? Bugzilla has multiple uses. The upstream project goes to some length describing it as a flexible tool. We in fact use it for multiple purposes. We use it for package review tickets...which are stictly speaking not "bugs" in a release. We most definitely use it primarily as a to-do list manager for package maintainers..from package birth to package death. The established workflow that we are using now is not and has never pretended to be an accurate audit trail of active defects in a given release. > I always thought that the bugzilla is for whole community, including > the users. Not just for pkg maintainers. No one has so far defined a workflow that requires an accurate audit of active deficiencies in any release. Closing bugs fixed rawhide certainly cause some annoyances because closed bugs are marginally harder to search for (because you have to request closed bugs to search through) when encountering the problem again and subsequently cause bugs to be refiled unnecessarily. The same goes for any closure condition that bodhi doesn't automatically perform when an update gets pushed to stable. -jef -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel