From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Please do not stabilize packages for arches you cannot test for
Date: Mon, 29 Dec 2003 17:16:51 +0000 [thread overview]
Message-ID: <20031229171651.5cc62a4b@snowdrop.home> (raw)
In-Reply-To: <200312291523.44286.pauldv@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
On Mon, 29 Dec 2003 15:23:33 +0100 Paul de Vrieze <pauldv@gentoo.org>
wrote:
| > Feedback please. I advocate this approach for 'minor' packages, i.e.
| > nothing fundamental to the working of the system. It's more suitable
| > for scripting language libraries and minor applications (e.g.
| > obscure window managers).
|
| A more appropriate option would be to allow users to test packages
| that have not been marked as broken on their arg and then have a
| policy that if at least two users have reported a package as stable,
| and an arch dev can compile it it will be marked testing, and stable
| if it has no problems within a reasonable time period.
This is basically how we do things for sparc already. For non-core
packages with sane dependencies, if it is reported as working by a user
(bugzilla or over irc) and it compiles then we'll usually keyword it up
pretty quickly. This is how we handle a lot of the more obscure
packages. "It works" reports are always welcomed :)
--
Ciaran McCreesh
Mail: ciaranm at gentoo.org
Web: http://dev.gentoo.org/~ciaranm
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-12-29 17:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 4:00 [gentoo-dev] Re: Please do not stabilize packages for arches you cannot test for Tom Payne
2003-12-29 14:23 ` Paul de Vrieze
2003-12-29 17:16 ` Ciaran McCreesh [this message]
2003-12-29 22:34 ` Jason Wever
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=20031229171651.5cc62a4b@snowdrop.home \
--to=ciaranm@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