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]

Re: GCC Release Status (2003-08-03)


> > 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).

R.


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