On Tue, 6 Apr 2004 23:13:18 +0200, David Neary [EMAIL PROTECTED] wrote:
Raphaël Quinet wrote:
There is another thing that could be cleaned up in Bugzilla: moving
all 1.3.x bugs that are in RESOLVED state to the CLOSED state and
adding a comment saying that the fix is part of the official release
2.0.0 (or 2.0.1 soon).
Personally I don't see the need. I've personally looked at the
milestones to see when bugs were fixed (and the comments), and I
have never really seen a benefit to having both resolved and
closed - in fact, in my company's installation of bugzilla we
reduced the lifecycle of bugs to 4 states - New, Assigned,
Resolved and Reopened, which suits our usage patterns fine.
As for the target milestones, they are not always reliable because
some bugs are fixed without having a target assigned to them, and some
others are fixed before the expected target milestone. At my company,
we use something else than bugzilla (alas!) but we have the equivalent
of resolved and closed: a bug is closed when the fix has been
verified and is part of an official product release, but before that
it is only resolved.
You mention a benefit to users, but I don't think personally that
users (in general) use bugzilla to an extent where this is a
large factor. Nor do people in general have a deep knowledge of
the nuances of resolved and closed.
I agree that non-developers do not care that much about resolved
vs. closed, but for 1.2.x I got some feedback from users who liked
the additional comment saying in which stable release a given bug was
fixed. I am guessing that it helped those who were not sure if they
had to upgrade to the latest release or if another version was good
enough for them. This is useful for those who rely on third-party
binary packages and may not always have the last version for their
platform.
I think that the overhead of going through the bugs and changing
them to CLOSED probably outweighs the benefit of it. But if you
feel otherwise, I don't mind (although slogging through 300
bugzilla mails is going to be a pain).
Yes, and updating the bugs is going to be a pain as well, because this
cannot be completely automated. But I think that it is useful anyway.
Before doing anything, I will wait a few more days and see if there
are other opinions posted here.
-Raphaël
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
