Re: patch/proposal: obsolete configurations in 3.1

["Kai Henningsen" <kaih at khms dot westfalen dot de>]

On 15 Apr 2002 at 10:05, Zack Weinberg wrote:

> I would like to avoid getting into a controversial policy debate two
> weeks before 3.1 is released.  Therefore, I think that in 3.1 we
> should deprecate only those targets that have no constituents at all.
> For 3.2 we can talk about doing a broader sweep.

For 3.2, how about a (published enough in advance, of course) policy 
that everything goes for which there isn't either a "successful 
built" report or submitted testresults for the last N releases (or 
possibly N months)?

I'm assuming this would also catch anything actively supported, 
because submitting testresults wouldn't be a significant burden on 
whoever does that support.

For a later version, that could then be strengthened to at least a 
successful bootstrap.

I'm assuming here that as long as a configuration does successfully 
bootstrap, keeping it around cannot be that big a burden - sort of 
proof by success.

To make that work, the list of "verified" configurations, with last-
verified-at version or date (whatever the actual criterion is), could 
be listed on a web page, so users can easily find out if submitting 
either report would be a bright idea to keep one's port active.

Something along these lines would, it seems to me, make unnecessary 
these long threads building lists of configurations that can removed 
this time.

"No, I still have one customer for this port!" - "Ok, where's your 
build report and/or testresults? You're still using 2.8? Then why 
should we care if 3.5 supports that config? Next!"

Regards - Kai Henningsen

-- 
http://www.cats.ms
Spuentrup CTI       Fon: +49 700 CALL CATS (=22 55 22 87)
Windbreede 12       Fax: +49 251 322312 99
D-48157 Muenster    Mob: +49 161 322312 1
Germany             GSM: +49 171 7755060