On 2017-12-14 13:58, Kent Fredric wrote: > On Wed, 13 Dec 2017 21:58:05 +0100 > Slightly modified suggestion: > > Add a flag called "autostabilize" with [unset], [y], [n] > > Default is 'unset', and if found unset after a given time, it flips to > y and the stable bot gets queued up. > > If its set to 'n', then stable bot never does anything. > > This way maintainers who want to rush the stablebot on things they > consider "safe" can get ahead of the queue.
Well, we kind of have that already with “Runtime testing required” (RTR). RTR=no stablereqs are good candidates for automation. If everything has been properly handled in the ebuild, then an emerge should succeed. And, RTR being set to “No” indicates that there aren’t any tests to perform other than those defined and handled within the ebuild. Restricting the set to RTR=no would eliminate special cases needing to be taken into consideration. Of course, RTR being unset or set to yes should be skipped. We could initially start with stablebot only adding a comment to a bug that it thinks it’s safe to stabilize the subject. This would give us some time to gain confidence in it and/or weed out the bugs.
signature.asc
Description: Digital signature
