Re: [gentoo-dev] Autobuilds go to /experimental and to /releases only when someone actually tests them

[yac]

-----BEGIN PGP SIGNED MESSAGE-----

Hash: SHA1



On Sat, 27 Jul 2013 00:13:37 -0400

"Rick \"Zero_Chaos\" Farina" <zerochaos@g.o> wrote:



> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 07/27/2013 12:08 AM, Matt Turner wrote:
> > (I sent this to gentoo-releng@. Resending to gentoo-dev@ for a
> > wider audience)
> >
> > Can we make autobuilds go to /experimental and then only move them
> > to /releases when someone actually tests them?
> >
> > Looking at bugzilla and listening in #gentoo-releng, it's kind of
> > embarrassing how often someone downloads a Live CD only to find out
> > that networking is totally broken by a udev upgrade, or something to
> > that effect.
> >
> > We don't commit version bumps straight to stable; I don't see why we
> > do with release media.
> >
>
> It's been an odd week for me agreeing with people but yeah, I
> completely agree.  I think we *need* to keep the autobuilds going as
> often as possible to detect obvious breakage, but there is no reason
> they shouldn't be marked experimental.
>
> The real question is, how realistic can we make a process of testing
> and moving to stable?


openSUSE is using [openQA] for automated testing of installation media

which is pretty need something that starts a machine in KVM and

then simulates the user via a keyboard events.



Last year there was also a talk about it on osc12 [2]



[openQA] http://openqa.opensuse.org/

[2] http://www.youtube.com/watch?v=57a9zmpA844



> - -Zero
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.19 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBAgAGBQJR80jxAAoJEKXdFCfdEflKhGYP/At7Xtd4bWcY1wrxl1oPYdNr
> vVfgqhmnveNqwhdERcp8InGLGoCDt+O3hvSzq4kX8qJXqizxPonP9ef1hJsnz0iw
> NgjMHiGiYp2NgmU6DB7X/VLH3RNF96WJMK/R2Qtk1tuN+Ftu1D6T5hP4MmTOuvta
> T2CvfYGFVAPZiY9+GLAmbe1LhjwlbJ8DnhbaamA7bK1D0ZhApWtRVtjk6unu+D5w
> XRG8tIDml5gUkZRVl4d9Bg1wxuMoPtOuY2ANr+RCJPRVMkexB1XCdAVzPF73EFx+
> 0Ns5TKi+vWyhzY6PElvA0xClj2wAK/enAkAmPZ8OvagnCLfmoqZUNyr4+Eupxclt
> 54pFMzpdR2KntmmFqS5ZBF8Q6nxz8GDhSm0H8+d1xTKxNcwKSlaAI7JkzBByWhKt
> MjFYNTVz7MD/MFpvpRt2tKg3BI6m/ZcgCQwnAJ9QjdtyhLA8/Km5+AA2tnN457V7
> qlpf+ipjDzb3G5Po1JXSMUidy8Uu6SvqHu8TwiJUy/mlKxjmPmrPPGfRpR32pWNT
> d/jE6IQAmiVjXWTDDBi0uZY8oUl5H0uroLFuA+//NtmGD8DWmV1fK0PYKLjUsE4X
> nWaCKn2qlF7d16mnJh1RweBjQjMmvRYutg62A3Jb9Ek9jXBIC4bYJa2VS2xoPpWy
> qZv8oon/9z336E5Uvamj
> =KaUO
> -----END PGP SIGNATURE-----
>


-----BEGIN PGP SIGNATURE-----

Version: GnuPG v2.0.19 (GNU/Linux)



iQEcBAEBAgAGBQJR86ybAAoJEIN+7RD5ejah990H/jHk6bDSJeRmkDwj0FLiIc3I

FbzwwaTug3DWpa1xegPTOK4Mxa2Nb7aVYfs4bZsQvQYrw+3WzvHmeYhfRiBNlU/B

yiVGJ5TcPQpYltrTKx/nOuEvkH9NTcv/woiuTQ/kRedZKmNAmD/iQPwbITzOgE5U

vCKyHtXGv9bwQbQBlHGNDHkinasMEGNio5uK/1XMjSxeRS9xmcAn1UNDc4OucEpA

ac9EwrJgIzWgVnqD9x/mGY+GwB+dFZWrVyeGlsfEyHrTkDGu7zMBwJPd7swCxGFT

ABLqts0EjbPnZIbihe962Tt/E73srEvgoHACib4D7P4sjB+X4leCQMu3D3RQVNs=

=yUYu

-----END PGP SIGNATURE-----