public inbox for gentoo-releng@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jorge Manuel B. S. Vicetto" <jmbsvicetto@gentoo.org>
To: gentoo-releng@lists.gentoo.org
Subject: Re: [gentoo-releng] Autobuilds go to /experimental and to /releases only when someone actually tests them?
Date: Mon, 29 Jul 2013 19:05:41 +0000	[thread overview]
Message-ID: <CADvE9N=3Ly2ifc0qUDCck+9c1y=qjhtjEYeP8NQPt1WAmf_7vg@mail.gmail.com> (raw)
In-Reply-To: <CAEdQ38EFHn02A4e6b_ZiW_EPJdSe6dNtT1cO_8DmgmuD-qKZgw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]

On Fri, Jul 26, 2013 at 4:24 AM, Matt Turner <mattst88@gentoo.org> wrote:

> Can we make autobuilds go to /experimental and then only move them to
> /releases when someone actually tests them?
>
>
Even though this sounds good and makes sense, if we don't even have enough
people to work on things now, this would only make things worse (imho).


> 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.
>
>
There's no way to deal with this breaks when those committing them don't
even warn us about them.


> We don't commit version bumps straight to stable; I don't see why we
> do with release media.
>
> Matt
>
>
The alternative here is the automated testing that I've talked about with
others on FOSDEM and Prague last year, but that still needs to be done.
Amongst other testing, the idea would be to pick the latest ISO and boot it
on some virtualization platform and catch the console output to ensure it
booted successfully and not tests failed.

Regards,

Jorge

[-- Attachment #2: Type: text/html, Size: 2016 bytes --]

  parent reply	other threads:[~2013-07-29 19:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26  4:24 [gentoo-releng] Autobuilds go to /experimental and to /releases only when someone actually tests them? Matt Turner
2013-07-26 12:24 ` Anthony G. Basile
2013-07-29 19:05 ` Jorge Manuel B. S. Vicetto [this message]
2013-07-29 20:38   ` Matt Turner
2013-09-15 19:52     ` Sebastian Pipping

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADvE9N=3Ly2ifc0qUDCck+9c1y=qjhtjEYeP8NQPt1WAmf_7vg@mail.gmail.com' \
    --to=jmbsvicetto@gentoo.org \
    --cc=gentoo-releng@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox