This is the mail archive of the
mailing list for the GCC project.
Re: GCC Release Status (2003-08-03)
- From: Richard Earnshaw <rearnsha at arm dot com>
- To: Daniel Berlin <dberlin at dberlin dot org>
- Cc: "Mark Mitchell" <mark at codesourcery dot com>, "Joe Buck" <jbuck at synopsys dot com>, gcc at gcc dot gnu dot org, Richard dot Earnshaw at arm dot com
- Date: Tue, 05 Aug 2003 10:36:20 +0100
- Subject: Re: GCC Release Status (2003-08-03)
- Organization: ARM Ltd.
- Reply-to: Richard dot Earnshaw at arm dot com
> > Anyhow, we certainly shouldn't change old, closed bugs. I just want
> > to keep
> > people from marking new bugs as targeted for 3.3.1.
> I can add this feature if you guys really want it, I just see it as a
> "don't do that" type thing that we're all smart enough not to do. Why
> would a developer target a new bug at an old release?
> Remember, users can't target bugs to milestones.
Can we have the concept of "obsolete milestones"? Ie they remain valid
(from an historical perspective), but aren't available in the pull-down
menu on the various bug pages (this stops the list growing excessively
long with obsolete options as time passes).