On Mon, Apr 5, 2010 at 11:24 PM, Denis Dupeyron <calc...@gentoo.org> wrote: > On Sun, Apr 4, 2010 at 3:16 AM, Nirbheek Chauhan <nirbh...@gentoo.org> wrote: > >> I see no reason whatsoever to keep it open. > > How about this one: preventing users from filing dupes. >
We already advise our users to check RESO bugs before filing bugs; and the advice seems to have trickled down quite well, and users only file duplicate bugs once before getting the idea. Overall, IMO it has worked. We only keep a single bug open for the entire GNOME 2.xx so people don't file dupes for that (we get a lot of dupes for that, but not specific packages). >> If we >> start doing that, we'll end up with tons of extra bugs on our hands. > > What's the big deal? You know you'll be adding/bumping the package at > some point. Just close the bug when you do so. It's certainly less > work than marking it RESOLVED FIXED once and then DUPLICATE many times > after that. > > The point of bugzilla is tracking bugs, not a tool to arbitrate a > pissing contest about who has the least bugs open. If you can't/don't > want to fix a bug that's OK, but it's not a good enough reason to > pretend it never existed. > That's not the point; as I have explained above; our purpose is to prevent bug reports for packages that will go in with the major release from being filed. We usually have a [Tracker] bug open for the major release anyway; so the choice is either RESO DUPLICATE against that, or RESO LATER. We often do the latter to prevent noise on the tracker bug, or if it hasn't been filed yet, and the user is doing a stupid zero day bump request (or a development version bump request). For packages that are not in the gnome set, or gnome external deps set, we obviously keep the bump request bug open. -- ~Nirbheek Chauhan Gentoo GNOME+Mozilla Team
