BEWARE: a problematic glibc made it to stable (F16)

Henrik Nordström henrik at
Mon Oct 24 00:47:16 UTC 2011

sön 2011-10-23 klockan 17:04 -0500 skrev Rex Dieter:

> The fail(*), imo, was with 12.999 going stable containing known-regressions.  
> So, any suggestions, if any, to prevent any similar series of events?

My suggestions:

Disable automatic push to stable when there is any negative karma,
requiring the package maintainer to initiate the push even if karma
kriteria have been met.

Don't automatically push to stable until at least X days (3?) have
passed, enabling sufficient time for regressions to be detected. Package
maintainer can initiate push earlier by "Push to stable" if needed and
confident there is no regressions.

Make "push to stable" require extra confirmation when there is negative
karma, making sure that whoever is initiating the push have actually
looked at why there is negative karma.


More information about the devel mailing list