On Tue, 01 Oct 2013 00:23:16 +0800
Patrick Lauer <[email protected]> wrote:
> On 09/30/2013 07:45 PM, Chí-Thanh Christopher Nguyễn wrote:
> > due to technical issues with the robo-stable scripts.
>
> > due to technical issues with the robo-stable scripts.
>
> let me summarize my response as "WAT"
I call, and raise you a "THIS".
> Maybe we should just have a cronjob that just does all that
> automatically?
Having been doing stabilisation for nearly eight years, I have often
*thought* about ways to automate architecture testing/stabilisation.
I have invested in tools and scripts that help me run certain steps
along the way. I have never invested time or effort in automating
the process entirely, because it will cause failures.
Actually looking at stabilisation targets (the relevance USE flags, code
in the actual ebuilds, DEPENDs), assessing the targets' importance (for
instance, in checking what RDEPENDs on them), and testing accordingly,
is the only way to ensure that a stabilisation request is sane and
doable, and only then can you execute it.
Since we have had automated stabilisation requests filed, it has
become even more important to not automate stabilisation itself.
Not automating the entire process involves more manual steps, and most
of the time it isn't very rewarding, but it does get the job done of
catching out nearly all of the superficial bugs (like, does this
library actually work with stable RDEPENDs).
jer
