Re: Bugzilla stuff (was: Re: 3.3.1 bug fix list ...)

[Daniel Berlin <dberlin at dberlin dot org>]

On Friday, July 25, 2003, at 12:53 PM, Joe Buck wrote:

> On Thu, Jul 24, 2003 at 09:40:35PM -0700, Mark Mitchell wrote:
>
> I wrote:
> > > To make the task of preparing release notes less painful, I'd like to
> > > get agreement that "target milestone" for a fixed bug means the 
> > > earliest
> > > planned release that will contain the fix.  That means that if a bug 
> > > is
> > > closed as fixed in 3.4, and it is then decided to backport the fix 
> > > for
> > > 3.3.2, the target milestone would be changed to compensate.
>
> Mark wrote:
> > I agree that this should be the policy.
>
> I've gone through and fixed a number of target milestones.
>
> I have questions about two bugs:
>
> 11282: it is still in assigned state, but the ChangeLog shows a patch
> and the log says "fixed the first bug for 3.3.1".  Does this mean that
> there is an additional unfixed bug?  Nathan?
>
> Second, 8986.  Is this still in 3.4?
>
> Finally, a couple of bugs are in CLOSED/FIXED state rather than
> RESOLVED/FIXED state.  We should be consistent here, right?  There
> doesn't seem to be a direct way to change the state to RESOLVED;
> does the bug have to be reopened first?

Actually, you've got it backwards, there are more bugs in the 
closed/fixed state than the resolved/fixed state.
But they should be resolved/fixed.

I'll take care of these.

mysql> select COUNT(*) from bugs where bug_status = 'closed' and 
resolution = 'fixed';
+----------+
| COUNT(*) |
+----------+
|     8109 |
+----------+
1 row in set (0.13 sec)

mysql> select COUNT(*) from bugs where bug_status = 'resolved' and 
resolution = 'fixed';
+----------+
| COUNT(*) |
+----------+
|      521 |
+----------+
1 row in set (0.22 sec)

mysql>
>