public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: wg-stable@gentoo.org, arch-leads@gentoo.org,
	Gentoo alpha AT <alpha@gentoo.org>,
	Gentoo AMD64 AT <amd64@gentoo.org>,
	amd64-fbsd@gentoo.org, Gentoo arm AT <arm@gentoo.org>,
	arm64@gentoo.org, Gentoo hppa AT <hppa@gentoo.org>,
	Gentoo ia64 AT <ia64@gentoo.org>,
	Gentoo m68k AT <m68k@gentoo.org>,
	Gentoo mips AT <mips@gentoo.org>, Gentoo ppc AT <ppc@gentoo.org>,
	Gentoo ppc64 AT <ppc64@gentoo.org>,
	Gentoo s390 AT <s390@gentoo.org>, Gentoo sh AT <sh@gentoo.org>,
	Gentoo sparc AT <sparc@gentoo.org>,
	Gentoo x86 AT <x86@gentoo.org>,
	x86-fbsd@gentoo.org
Subject: Re: [gentoo-dev] [RFC] Future of gentoo's stable and unstable trees: what are your thoughts?
Date: Fri, 28 Jul 2017 16:24:02 -0500	[thread overview]
Message-ID: <20170728212402.GA11006@whubbs1.gaikai.biz> (raw)
In-Reply-To: <CA+CSuAJ=3bgJRWSiWQHcamrht=SKum676KTjXC0kgbGodHX4Uw@mail.gmail.com>

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

On Thu, Jul 27, 2017 at 07:03:25PM -0500, Denis Dupeyron wrote:
> On Thu, Jul 27, 2017 at 6:41 PM, Rich Freeman <rich0@gentoo.org> wrote:
> >
> > When in the last 16 years was this 2 year period of running stable?
> > The general state of QA has varied quite a bit over that time.
> >
> 
> I would say 3 or 4 years ago, roughly.
> 
> 
> > running unstable systemd has been
> 
> 
> Running unstable doesn't mean being stupid.
 
Exactly. If you are running unstable, you are expected to know how to
pick up the pieces if something breaks. Unstable is not meant for
people who aren't comfortable with occasional breakage.

> > If unstable never breaks chances are we aren't actually using it for its
> > intended purpose, not that we
> > should be deliberately breaking things.
> 
> There's this idea that unstable should break. But the initial idea was that
> unstable is what should be sent straight to stable, barring the occasional
> mistake. Unstable was never meant for ebuilds in development and very much
> in flux because of that. That's what package masks are for.

package masks are specifically for things that are known to cause major
system breakages.

Maintainers test things to the best of their
ability before putting them in the tree, but may not cover all possible
test cases, so packages go to the ~arch tree to get much wider coverage
before they are deamed stable. That is why there is a  recommended delay
of 30 days before the package moves to stable.

William


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2017-07-28 21:24 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24 21:22 [gentoo-dev] [RFC] Future of gentoo's stable and unstable trees: what are your thoughts? Sergei Trofimovich
2017-07-24 21:52 ` [gentoo-dev] " Pacho Ramos
2017-07-24 23:22 ` [gentoo-dev] " Peter Stuge
2017-07-24 23:52   ` Rich Freeman
2017-07-25  4:34     ` [gentoo-dev] " Duncan
2017-07-25  6:26       ` Hans de Graaff
2017-07-25  6:18   ` [gentoo-dev] " Hans de Graaff
2017-07-25  9:18     ` Pacho Ramos
2017-07-25 11:54       ` Michał Górny
2017-07-25 12:15         ` Pacho Ramos
2017-07-25 13:19           ` Michał Górny
2017-07-25 13:23             ` Pacho Ramos
2017-07-25 11:26     ` Rich Freeman
2017-07-25  7:44   ` Sergei Trofimovich
2017-07-28 10:44   ` Andreas K. Huettel
2017-07-28 12:45     ` Marek Szuba
2017-07-28 13:10     ` Sam Jorna (wraeth)
2017-07-28 19:59       ` William L. Thomson Jr.
2017-07-28 21:21         ` David Seifert
2017-07-31  0:28         ` Sam Jorna
2017-07-31  0:40           ` Benda Xu
2017-07-31  2:44           ` William L. Thomson Jr.
2017-07-31  2:56             ` Sam Jorna
2017-07-31 15:00               ` William L. Thomson Jr.
2017-07-31 12:59             ` Andreas K. Huettel
2017-07-31 14:43               ` William L. Thomson Jr.
2017-07-31 14:47                 ` David Seifert
2017-07-28 19:44     ` Alec Warner
2017-07-29  1:05       ` Rich Freeman
2017-07-31 14:52         ` Alec Warner
2017-07-31 15:11           ` Rich Freeman
2017-07-31 16:51             ` Peter Volkov
2017-08-01  0:24             ` [gentoo-dev] " Duncan
2017-08-01  0:55               ` Rich Freeman
2017-08-01  1:45                 ` Duncan
2017-07-31 16:44           ` [gentoo-dev] " Michał Górny
2017-07-29  4:18       ` Daniel Campbell
2017-07-29 16:41         ` Mart Raudsepp
2017-07-29 19:10           ` David Seifert
2017-07-29 18:03     ` Andrew Savchenko
2017-07-25  7:22 ` Dirkjan Ochtman
2017-07-25 13:10   ` [gentoo-dev] " Michael Palimaka
2017-07-25 13:22     ` Rich Freeman
2017-07-25 20:16       ` Daniel Campbell
2017-07-25 13:36     ` Pacho Ramos
2017-07-25 14:15     ` Peter Stuge
2017-07-29 18:08   ` [gentoo-dev] " Christopher Head
2017-07-31  6:49     ` R0b0t1
2017-07-25  9:03 ` [gentoo-dev] " Agostino Sarubbo
2017-07-25 19:45   ` Markus Meier
2017-07-25 20:12     ` Rich Freeman
2017-07-26  5:49   ` Hans de Graaff
2017-07-25 12:59 ` Michael Palimaka
2017-07-25 13:30   ` Pacho Ramos
2017-07-25 13:51   ` Michał Górny
2017-07-25 14:13 ` [gentoo-dev] " Michał Górny
2017-07-25 14:28   ` Rich Freeman
2017-07-27 23:12 ` Denis Dupeyron
2017-07-27 23:41   ` Rich Freeman
2017-07-28  0:03     ` Denis Dupeyron
2017-07-28 21:24       ` William Hubbs [this message]
2017-07-29 10:24   ` Andrew Savchenko
2017-07-28 20:10 ` William L. Thomson Jr.
2017-07-28 21:12   ` A. Wilcox
2017-07-28 21:41     ` William L. Thomson Jr.
2017-07-29 13:41     ` Andreas K. Huettel
2017-07-28 21:45   ` [gentoo-dev] " Duncan
2017-07-28 21:56     ` William L. Thomson Jr.
2017-07-29 19:44       ` Walter Dnes

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=20170728212402.GA11006@whubbs1.gaikai.biz \
    --to=williamh@gentoo.org \
    --cc=alpha@gentoo.org \
    --cc=amd64-fbsd@gentoo.org \
    --cc=amd64@gentoo.org \
    --cc=arch-leads@gentoo.org \
    --cc=arm64@gentoo.org \
    --cc=arm@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=hppa@gentoo.org \
    --cc=ia64@gentoo.org \
    --cc=m68k@gentoo.org \
    --cc=mips@gentoo.org \
    --cc=ppc64@gentoo.org \
    --cc=ppc@gentoo.org \
    --cc=s390@gentoo.org \
    --cc=sh@gentoo.org \
    --cc=sparc@gentoo.org \
    --cc=wg-stable@gentoo.org \
    --cc=x86-fbsd@gentoo.org \
    --cc=x86@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