On 2017-12-13 18:51, William Hubbs wrote: > In theory, this is correct. However, when maintainers don't stabilize > packages and no one else does either, our stable tree suffers.
I agree but we have to pay attention that we don't stabilize packages at all costs because otherwise they would never go stable. If this is the problem then we should discuss stabilization at all. What do people expect from something marked stable vs. reality. ;) And in this case I would prefer a system like Debian SID -> Testing supported by build bots. I can think of 2 variants: a) Once maintainer files a stabilization request, a build bot will pick up the bug and try building the package in a chroot per architecture. If everything passes build bot will mark the version stable for the tested architecture. A flag or a blacklist could prevent build bot stabilization. b) Because not all devs care about stable Gentoo, I would recommend auto-stabilization: I.e. if a package is in the repository for x days build bot would try to build the package and mark the package stable if everything passes. If for some reason maintainer want to block a specific version they could create a bug or set a flag in an already existing bug which will cause build bot to ignore this version. -- Regards, Thomas Deutschmann / Gentoo Linux Developer C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5
signature.asc
Description: OpenPGP digital signature
