public inbox for gentoo-releng@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-releng@lists.gentoo.org
Subject: Re: [gentoo-releng] Re: Free-standing Portage / Recent stage3 tarballs / Beta
Date: Sat, 02 Feb 2008 22:13:35 -0800	[thread overview]
Message-ID: <1202019215.14162.61.camel@inertia.twi-31o2.org> (raw)
In-Reply-To: <1202018207.31718.1234762467@webmail.messagingengine.com>

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

On Sat, 2008-02-02 at 21:56 -0800, davecode@nospammail.net wrote:
> > The stage tarballs are *never* ~arch. We have talked about doing automated 
> > builds, but we're not releasing them for public consumption, since there will be 
> > absolutely *zero* QA done on them.
> 
> Of course not; I didn't mean you replace official releases with ~arch! 
> I only meant that, like Debian et al, there be regular tarballs for
> eager testers.  That seems more sensible that starting testing from a
> year-old tarball.  Some others might test in kexec/vmware/chroot or
> whatever.

Ehh, we'd never release ~arch tarballs.  If we were to do something like
this, it would be weekly stable tarballs.  There's no guarantee that
~arch is even consistent.  With stable, there's at least the testing of
the arch teams.

> > why exactly do PPC boxes need the newest everything?
> 
> Sigh.  I'd rather not go there.  Suffice to say ~arch is why we're here.
>  The current ~arch is turning into 2008.0 anyway, so that's what where
> we can help QA Gentoo.

No, it isn't.

I think your idea of how Gentoo releases work is a bit skewed.
Everything comes from stable.  Always.

-- 
Chris Gianelloni
Release Engineering Strategic Lead
Games Developer

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-02-03  6:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-03  4:31 [gentoo-releng] Free-standing Portage / Recent stage3 tarballs / Beta davecode
2008-02-03  5:16 ` Andrew Gaffney
2008-02-03  5:56 ` [gentoo-releng] " davecode
2008-02-03  6:13   ` Chris Gianelloni [this message]
2008-02-03  8:37 ` davecode
2008-02-03  8:46   ` Christian Faulhammer
2008-02-03  8:48   ` Rémi Cardona
2008-02-03 12:19     ` Markus Hauschild
2008-02-03 17:16       ` Alex Howells
2008-02-03 18:27         ` M. Edward (Ed) Borasky
2008-02-03 22:44           ` Alex Howells
2008-02-04  4:28             ` M. Edward (Ed) Borasky
2008-02-04 16:42               ` Alex Howells
2008-02-04 17:17               ` Chris Gianelloni
2008-02-05  2:58                 ` M. Edward (Ed) Borasky
2008-02-04  5:40 ` [gentoo-releng] " keith
2008-02-05  7:35 ` [gentoo-releng] " davecode
2008-02-05 13:57   ` M. Edward (Ed) Borasky
2008-02-05 14:01     ` Dale
2008-02-05 14:21       ` Alex Howells
2008-02-05 14:29         ` Dale
2008-02-05 16:44   ` Chris Gianelloni

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=1202019215.14162.61.camel@inertia.twi-31o2.org \
    --to=wolf31o2@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