public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jeroen Roovers <jer@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: Proposal for how to handle stable ebuilds
Date: Tue, 11 Nov 2008 17:24:50 +0100	[thread overview]
Message-ID: <20081111172450.04e02b38@epia.jer-c2.orkz.net> (raw)
In-Reply-To: <pan.2008.11.11.16.06.02@cox.net>

On Tue, 11 Nov 2008 16:06:02 +0000 (UTC)
Duncan <1i5t5.duncan@cox.net> wrote:

> If it's a "production, critical, important" system, then what is one 
> doing installing updates on it directly without verifying them on a 
> generally identical test system first?

Now you're ridiculing the idea of having a "production/ critical/
important" system. Most of our users probably use a single Gentoo
machine (I see many cases where users have multiple machines, but only
one running Gentoo, or have one machine running several operating
systems), and for them an important system is one that they cannot
readily replace. Words like "production", "critical" and "important"
can be applied as easily to the state of a company's or nation's
system as to a single person's.

The stable branch has never been about commercial systems and their
stringent requirements[1] - it's all about this level of quality that
has users up in arms about one package blocking another or one package
requiring half the system to be rebuilt at a rate of no more than once a
year[2].


Kind regards,
     jer


[1] We've had calls for an über-stable project in the past that would
lock down versions and backport patches for enterprise systems.
[2] I.e. when we break the promise of [3].
]3] http://www.gentoo.org/main/en/philosophy.xml



  reply	other threads:[~2008-11-11 16:25 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-10 18:13 [gentoo-dev] Proposal for how to handle stable ebuilds Mark Loeser
2008-11-10 18:23 ` Ciaran McCreesh
2008-11-10 18:23 ` Mart Raudsepp
2008-11-10 20:32   ` Steev Klimaszewski
2008-11-10 21:16 ` Jeremy Olexa
2008-11-10 21:57 ` Santiago M. Mola
2008-11-11  0:24 ` Jose Luis Rivero
2008-11-11  1:13   ` Mark Loeser
2008-11-11  9:31     ` Jose Luis Rivero
2008-11-11  1:21   ` Richard Freeman
2008-11-11  8:56     ` Peter Volkov
2008-11-11 10:18     ` Jose Luis Rivero
2008-11-11 13:49       ` Ferris McCormick
2008-11-11 16:06       ` [gentoo-dev] " Duncan
2008-11-11 16:24         ` Jeroen Roovers [this message]
2008-11-11 17:26           ` Duncan
2008-11-11 17:55             ` Ferris McCormick
2008-11-11 18:12             ` Jeroen Roovers
2008-11-11 21:03               ` Duncan
2008-11-13 17:38 ` [gentoo-dev] " Tobias Scherbaum
2008-11-15 13:02   ` Matti Bickel
2008-11-17 18:08     ` Tobias Scherbaum
2008-11-17 19:03       ` [gentoo-dev] " Duncan
2008-12-11  5:35       ` [gentoo-dev] " Donnie Berkholz
2008-11-17  0:38 ` [gentoo-dev] " Ryan Hill
2008-11-17 15:10   ` Daniel Gryniewicz
2008-11-18  1:08     ` Ryan Hill
2008-11-18 16:57       ` Daniel Gryniewicz
2008-11-18 17:50         ` Ciaran McCreesh
2008-11-18 20:31           ` Daniel Gryniewicz
2008-11-18 21:18         ` Ryan Hill
2008-11-18 22:04           ` Daniel Gryniewicz
2008-11-18 22:45             ` Ryan Hill
2008-11-30 22:59 ` Ryan Hill
2008-12-01  7:49   ` Peter Volkov
2008-12-11  5:37 ` [gentoo-dev] " Donnie Berkholz

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=20081111172450.04e02b38@epia.jer-c2.orkz.net \
    --to=jer@gentoo.org \
    --cc=gentoo-dev@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