From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 83F911381F3 for ; Mon, 29 Jul 2013 19:05:47 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 35CCFE0962; Mon, 29 Jul 2013 19:05:43 +0000 (UTC) Received: from mail-qe0-f54.google.com (mail-qe0-f54.google.com [209.85.128.54]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id B5DECE0962 for ; Mon, 29 Jul 2013 19:05:42 +0000 (UTC) Received: by mail-qe0-f54.google.com with SMTP id 1so2530913qee.41 for ; Mon, 29 Jul 2013 12:05:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=AS+KT6kfB69miGl5vWfWP7q478fc1HdmRBGbfhLaPQ0=; b=XyRJEOSceMY0hGrBRs3C+hbXC82ksmqUNoapZ+uwhnz7twgPMOfeS2wq5Vx1YzUm0B US0vbU3U5xZOa4PQmalBkbWXDNfi8moW23zJQsPq36XTeIJUb0nBY2F4goKCnH6BmXZr nX6Ve8DYgip/4QyjQsNzcfXLCHTKSuzcLbC5+BT5MKIiQNIbMoPdSWnDR+ueZAgtP6i5 S/l6MTxnbk9jZAueW+QH/8mCUAqI9lDZ+EeIRt60MfbQ7gzHRKZdP7zUtvTW0pR8/H4I jPxU4kVDf1LXHx8wXbyRP2xGWX1+/BeUxQLkhhPGHWU3GFu/6ZiVldRjv80BegvvwDHh XKZA== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-releng@lists.gentoo.org Reply-to: gentoo-releng@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.224.67.202 with SMTP id s10mr72817595qai.66.1375124741760; Mon, 29 Jul 2013 12:05:41 -0700 (PDT) Sender: jmbsvicetto@gmail.com Received: by 10.49.63.37 with HTTP; Mon, 29 Jul 2013 12:05:41 -0700 (PDT) In-Reply-To: References: Date: Mon, 29 Jul 2013 19:05:41 +0000 X-Google-Sender-Auth: Qf0xxDmU2KYIbUfxwFHZJKzWb-k Message-ID: Subject: Re: [gentoo-releng] Autobuilds go to /experimental and to /releases only when someone actually tests them? From: "Jorge Manuel B. S. Vicetto" To: gentoo-releng@lists.gentoo.org Content-Type: multipart/alternative; boundary=001a11c31246c12c3404e2ab2d53 X-Archives-Salt: d6a42631-fdff-4d19-8810-faa4a37ebc88 X-Archives-Hash: f74a72a33fb0c787893dc5889ed3d553 --001a11c31246c12c3404e2ab2d53 Content-Type: text/plain; charset=ISO-8859-1 On Fri, Jul 26, 2013 at 4:24 AM, Matt Turner 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 --001a11c31246c12c3404e2ab2d53 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

= On Fri, Jul 26, 2013 at 4:24 AM, Matt Turner <mattst88@gentoo.org&g= t; wrote:
Can we make autobuilds go to /experimental a= nd 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).
=A0
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 b= reaks when those committing them don't even warn us about them.
=A0
We don't commit version bumps straight to stable; I don't see why w= e
do with release media.

Matt


The a= lternative here is the automated testing that I've talked about with ot= hers on FOSDEM and Prague last year, but that still needs to be done.
Amongst other testing, the idea would be t= o 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.<= br>
Regards,

Jorge
--001a11c31246c12c3404e2ab2d53--