From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Why don't you just ...
Date: Wed, 11 Apr 2007 13:15:39 -0400 [thread overview]
Message-ID: <1176311739.8755.99.camel@inertia.twi-31o2.org> (raw)
In-Reply-To: <1176310259.5744.19.camel@sputnik886.lnet>
[-- Attachment #1: Type: text/plain, Size: 831 bytes --]
On Wed, 2007-04-11 at 18:50 +0200, Matthias Langer wrote:
> a system where functionality is critical.
I would expect any such system to have a decent administrator that is
versed in best practices, such as actually testing upgrades before
applying them on any such server.
GLEP42 is not designed to let admins be lazy. It is designed to get
important information to our users. People with critical systems will
still need to perform the same level of verification before doing any
upgrades, no matter how much information we give them. The idea here is
to warn people about potential changes ahead of time so they know where
to focus their time.
--
Chris Gianelloni
Release Engineering Strategic Lead
Alpha/AMD64/x86 Architecture Teams
Games Developer/Council Member/Foundation Trustee
Gentoo Foundation
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-04-11 17:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 22:56 [gentoo-dev] Why don't you just Benedikt Boehm
2007-04-11 1:26 ` Christopher Sawtell
2007-04-11 1:52 ` Andy Dalton
2007-04-11 2:49 ` Matthias Langer
2007-04-11 3:03 ` Alec Warner
2007-04-11 11:47 ` [gentoo-dev] " Christian Faulhammer
2007-04-11 16:50 ` Matthias Langer
2007-04-11 17:15 ` Chris Gianelloni [this message]
2007-04-11 5:17 ` [gentoo-dev] " Luca Barbato
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=1176311739.8755.99.camel@inertia.twi-31o2.org \
--to=wolf31o2@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