Marc Haber, on Sun 13 Nov 2016 11:30:18 +0100, wrote: > On Wed, 9 Nov 2016 14:01:13 +0000, Ian Jackson > <ijack...@chiark.greenend.org.uk> wrote: > >If it turns out to be a more common problem and there are many > >packages affected, then this would mean delays to the stretch release, > >indeed. > > One of my issues is that this new policy means a switch from "we'll > release when it's ready" to "we'll sacrifice package list completeness > of our release for a timely release", which is a rather radical > change.
We have always had to sacrifice packages to get something released. You can't release 10,000 packages at the same time if you don't make sacrifices. It just has moved from "arbitrary" to "not maintain closely enough". Samuel
