On Tue, 20 Aug 2013 22:16:34 +0200
hasufell <hasufell@gentoo.org> wrote:

> On 08/20/2013 08:19 PM, William Hubbs wrote:
> > 
> > My question is, how can we improve our stabilization
> > procedures/policies so we can convince people not to run production
> > servers on ~arch and keep the stable tree more up to date?
> > 
> 
> Why convince them? They have been warned and it's their own problem.
> 
> I don't see any BIG problem in our current stabilization procedure.
> Scripts for auto-filing stablereqs seem wrong to me. It's not just
> about "it was 30 days in the tree without a bug". The maintainer has
> to know about upstream bug reports and other crap that might be going
> on.
> 
> Such things to speed up the procedure will only make it worse.

+1 at most it helps as a reminder to me; but indeed, a lot of these
reminders are false positive. What we really should do instead is look
for the worst offenders; in other words, which packages haven't been
stabilized for ages, which have a stable version of half a year ago?

See `imlate --mtime=180 -s | less`. (From app-portage/gentoolkit-dev)

I quote:

> ==============================================
> 4392 Stable candidates for 'gentoo' on 'amd64'
> ==============================================

Let's double the number to a year ago (360 instead of 180), I quote:

> ==============================================
> 2728 Stable candidates for 'gentoo' on 'amd64'
> ==============================================

And also get an impression of 3 months (90 instead of 180), I quote:

> ==============================================
> 6065 Stable candidates for 'gentoo' on 'amd64'
> ==============================================

At least the numbers for the year sound like something we will want to
deal with; from there, we could try to keep half a year low. And after
a while, we might end up ensuring stabilization within 3 months.

That's still three times more than our intended stabilization delay...

-- 
With kind regards,

Tom Wijsman (TomWij)
Gentoo Developer

E-mail address  : TomWij@gentoo.org
GPG Public Key  : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2  ABF0 95B2 1FCD 6D34 E57D