Re: Bug#484129: release.debian.org: packages in tasks should be fixed in priority and removed in last resort after discussion
Mike Bird wrote:
> On Mon June 2 2008 09:27:08 Raphael Hertzog wrote:
>> I think it's important that the release team supports the work done on
>> tasksel (by the d-i team) by not removing unilateraly packages which are
>> listed in tasks. They have been added there in the first place for a
>> reason, it would be nice to be able to offer a continued user experience
>> from release to release and not have significant functionalities
>> disappear just because we (as Debian, not as release team) have not been
>> able to recruit volunteers for the corresponding packages.
> A good idea but it doesn't go far enough. Personally I don't find
> d-i tasks to be any more important than "the packages I need", and
> I suspect millions of Debian users have equivalent opinions.
That's what rc-alert is for.
> Packages are summarily removed from Testing far too often, and then
> find it much harder to return because they are then "new". I don't
> know if the algorithms were changed six months ago, but starting
> around the turn of the year we've frequently had to resort to Sid
> when replicating existing configurations onto new boxes. This is a
> bar to adoption by new users, and new users are usually desktop or
> laptop users who need Testing for hardware support.
Accusing won't help at all, no the algorithms are not changed. Fixing RC
bugs for instance in the list you get from rc-alert might prevent your
apparently changing view...
> Artificially lowering the RC count in Testing is not always
> preferential to keeping Testing in a state amenable to testing.
You say yourself that it's not artificially as RC bugs in "new" packages
don't get that easily in testing anymore...