On Wed, Dec 13, 2017 at 09:58:05PM +0100, Thomas Deutschmann wrote: *snip*
> 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. I tend to like this better. Let's try to move away from filing stable requests for new versions of packages once an old version is stable and have a way to block newer versions from going stable. Maybe buildbot could check to see if there is a bug open against the version it is looking at, then check the keywords or severity of that bug and use one or the other of those to decide whether or not to skip stabilizing that version of the package. I think something else we should add to this is that buildbot should do nothing if there isn't already a stable version of the package on the architecture it is testing. In other words, the first stabilization for a package on an architecture should be done the way we currently do them, by filing a stable request then using the current stabilization process. William
signature.asc
Description: Digital signature
