Re: Obsolete/broken targets in 4.0.0

[Mark Mitchell <mark at codesourcery dot com>]

Joe Buck wrote:
> On Thu, Jan 20, 2005 at 11:59:37PM -0800, Mark Mitchell wrote:
>
> > Eric Botcazou wrote:
> >
> > > Hi Mark,
> > >
> > > What is the procedure to mark a target as obsolete or to remove a broken 
> > > target for 4.0.0?  Some SPARC targets (namely sparclite-elf, sparclite-coff, 
> > > sparc86x-elf and sparc-openbsd) have been broken (do not build) since at 
> > > least 2 releases (from 3.3 onwards).  Can I remove them from mainline or 
> > > should they first go through a period of obsolescence?
> >
> > Good question.  I believe our usual procedure is to announce them 
> > obsolete in one release, and remove them in the next.  So, you should 
> > put an announcement in the 4.0 release notes (Gerald can tell you where 
> > exactly!), and then remove them after 4.0 branches.
>
>
> If we don't obsolete them, we should do the users a service and make sure
> that the release notes say that they do not work, and in fact that they
> don't even build.

True.

And I have no problem with marking them obsolete in 3.4.4.  But, I do 
think that it's a bit short notice to obsolete in 3.4.4 and remove in 4.0.

--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304