This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


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?


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]