public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] apache and ~arch
Date: Tue, 15 Mar 2005 15:20:34 +0000	[thread overview]
Message-ID: <20050315152034.738e3a12@snowdrop> (raw)
In-Reply-To: <4236A61A.2020905@gentoo.org>

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

On Tue, 15 Mar 2005 10:08:42 +0100 Sven Vermeulen <swift@gentoo.org>
wrote:
| Marius Mauch wrote:
| > http://planet.gentoo.org/developers/hollow/2005/03/14/apache_dithering
| > "... and users using testing may not complain if things break."
| > 
| > That's the real problem.
| 
| They *should* complain, constructively, on a bugreport, stating the 
| issue and how they could resolve it. If people wouldn't be allowed to 
| reply to ~arch bugs, then why do we have ~arch?

We have ~arch for things that aren't well tested but aren't believed to
be broken. So, some midpoint is needed on the ~arch being broken thing.
On the one hand, it's not suitable for running on production kit, so
complaints about things which aren't known to be broken being added to
~arch aren't particularly viable. On the other hand, constructive useful
bug reports about breakages in ~arch that the maintainer doesn't know
about *are* useful, since they'll let the maintainer know that the
package isn't ready to go stable.

Probably easiest to think of ~arch as meaning "candidate for arch after
more testing".

-- 
Ciaran McCreesh : Gentoo Developer (Vim, Fluxbox, shell tools)
Mail            : ciaranm at gentoo.org
Web             : http://dev.gentoo.org/~ciaranm


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

  reply	other threads:[~2005-03-15 15:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-13 17:24 [gentoo-dev] apache and ~arch Grant Goodyear
2005-03-14  0:17 ` kang
2005-03-14  9:23 ` Michael Stewart
2005-03-14 15:56   ` Grant Goodyear
2005-03-14 14:43 ` Ciaran McCreesh
2005-03-14 15:39   ` Christian Parpart
2005-03-14 16:57   ` Jochen Maes
2005-03-14 17:17     ` Marius Mauch
2005-03-15  9:08       ` Sven Vermeulen
2005-03-15 15:20         ` Ciaran McCreesh [this message]
2005-03-14 17:20     ` Ciaran McCreesh
2005-03-22 13:50 ` Paul de Vrieze
2005-03-22 14:32   ` Aaron Walker

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=20050315152034.738e3a12@snowdrop \
    --to=ciaranm@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-dev@robin.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