From: Simon Stelling <blubb@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] ekeyword and ordering
Date: Tue, 07 Jun 2005 13:23:57 +0200 [thread overview]
Message-ID: <42A583CD.2090201@gentoo.org> (raw)
In-Reply-To: <20050606222623.GI9084@kaf.zko.hp.com>
Hi,
Aron Griffis wrote:
> - A few people, myself included, pointed out that there's some
> valuable information available when keywords are always added to
> the end rather than being alphabetized. In particular, the
> concept of a "maintainer arch" is possible, in which the first
> arch in the list is supposed to indicate general stability of
> the ebuild, a leader for other arches to follow.
>
> - Some people disagreed with the "maintainer arch" concept. They
> felt that the arch teams do a better job of testing than some
> maintainers, and there's no point waiting for a maintainer to
> decide something is stable.
>From [1]:
|When a package version has proved stable for sufficient time and the
|Gentoo maintainer of the package is confident that the upgrade will not
|break a regular Gentoo user's machine, then it can be moved from ~ARCH
|to ARCH. An indication of the package's stability would be no verified
|or unresolved bug report for a month after the version's introduction.
If that policy is dropped, I'd prefer alpha, otherways append.
Greetings,
blubb
[1] http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=3&chap=1
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
blubb@gentoo.org
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-06-07 11:23 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 22:26 [gentoo-dev] ekeyword and ordering Aron Griffis
2005-06-06 22:41 ` Mike Frysinger
2005-06-06 22:49 ` Stephen P. Becker
2005-06-07 12:16 ` Luca Barbato
2005-06-07 20:58 ` Danny van Dyk
2005-06-09 13:19 ` foser
2005-06-09 13:37 ` Lars Weiler
2005-06-09 15:59 ` [gentoo-dev] " Duncan
2005-06-09 15:29 ` [gentoo-dev] " Danny van Dyk
2005-06-09 15:50 ` Stephen P. Becker
2005-06-10 14:55 ` foser
2005-06-10 16:33 ` Mike Frysinger
2005-06-11 8:15 ` foser
2005-06-11 8:28 ` Jason Stubbs
2005-06-11 8:48 ` foser
2005-06-11 15:21 ` Joshua Baergen
2005-06-11 16:31 ` Diego 'Flameeyes' Pettenò
2005-06-11 18:00 ` Joshua Baergen
2005-06-11 9:06 ` Bryan Oestergaard
2005-06-11 18:46 ` Aron Griffis
2005-08-01 17:06 ` foser
2005-08-01 17:43 ` Aron Griffis
2005-06-11 20:37 ` Mike Frysinger
2005-06-10 17:19 ` Aron Griffis
2005-06-11 0:04 ` Georgi Georgiev
2005-06-11 12:48 ` Aron Griffis
2005-06-12 0:39 ` Georgi Georgiev
2005-06-12 2:18 ` Aron Griffis
2005-06-06 22:43 ` [gentoo-dev] " Michael Sterrett -Mr. Bones.-
2005-06-09 13:06 ` foser
2005-06-06 22:47 ` [gentoo-dev] " Lars Weiler
2005-06-07 3:19 ` Aaron Walker
2005-06-07 18:35 ` Donnie Berkholz
2005-06-09 13:10 ` foser
2005-06-09 16:49 ` Maurice van der Pot
2005-06-07 11:23 ` Simon Stelling [this message]
2005-06-07 14:04 ` Aron Griffis
2005-06-07 14:20 ` Diego 'Flameeyes' Pettenò
2005-06-07 15:15 ` Aron Griffis
2005-06-07 15:30 ` Diego 'Flameeyes' Pettenò
2005-06-07 22:35 ` Chris Gianelloni
2005-06-07 16:49 ` Michael Cummings
2005-06-07 18:38 ` Aron Griffis
2005-06-07 22:31 ` Chris Gianelloni
2005-06-07 22:32 ` Diego 'Flameeyes' Pettenò
2005-06-07 21:32 ` Marcus D. Hanwell
2005-06-07 21:44 ` Aron Griffis
2005-06-07 21:56 ` Olivier Crete
2005-06-07 22:11 ` Marcus D. Hanwell
2005-06-07 23:58 ` Lars Weiler
2005-06-07 22:18 ` Aron Griffis
2005-06-09 13:01 ` foser
2005-06-08 14:44 ` Jason Wever
2005-06-08 15:39 ` Joseph Jezak
2005-06-08 16:18 ` Marcus D. Hanwell
2005-06-08 16:23 ` Jason Wever
2005-06-07 23:07 ` Ferris McCormick
2005-06-08 0:25 ` Donnie Berkholz
2005-06-08 13:15 ` Chris Gianelloni
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=42A583CD.2090201@gentoo.org \
--to=blubb@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