From: Brad Laue <brad@brad-x.com>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Is there a process for marking ebuilds stable?
Date: 13 Apr 2003 18:25:15 -0400 [thread overview]
Message-ID: <1050272714.30123.5.camel@localhost> (raw)
Given the increasing size of the portage tree I'm becoming concerned
about the rate at which ebuilds move from the unstable ~arch keyword to
the stable one.
Has a formalized process been discussed for this? The first thing that
comes to mind is a set of tinderboxes designed to build packages with
predictable flags sending reports to each ebuild maintainer.
The second is more practical and within reach; advocacy of
stable.gentoo.org, and a policy of accepting a package as stable when
five or more users have vouched for it and two weeks have passed without
a bug report.
These are rough ideas, I'd love to hear some input on them. Any
thoughts?
--
// -- http://www.BRAD-X.com/ -- //
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2003-04-13 22:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-13 22:25 Brad Laue [this message]
2003-04-13 23:00 ` [gentoo-dev] Is there a process for marking ebuilds stable? Rainer Groesslinger
2003-04-13 23:07 ` Rainer Groesslinger
2003-04-13 23:07 ` Jon Portnoy
2003-04-14 9:31 ` Rainer Groesslinger
2003-04-14 7:32 ` Fredrik Jagenheim
2003-04-14 9:00 ` Michael Kohl
2003-04-14 11:04 ` Fredrik Jagenheim
2003-04-14 16:29 ` Mikael Andersson
2003-04-14 20:31 ` Alec Berryman
2003-04-14 21:48 ` Brad Laue
2003-04-14 21:58 ` Alec Berryman
2003-04-15 11:07 ` Mikael Andersson
2003-04-14 22:03 ` Brad Laue
2003-04-14 15:07 ` Brad Laue
2003-04-14 19:39 ` C. Brewer
2003-04-15 6:21 ` Abhishek Amit
2003-04-15 9:09 ` Fredrik Jagenheim
2003-04-16 0:34 ` C. Brewer
2003-04-15 13:53 ` Brad Laue
-- strict thread matches above, loose matches on Subject: below --
2003-04-15 2:08 Todd Wright
2003-04-15 2:30 ` Jon Portnoy
2003-04-15 5:41 ` Dylan Carlson
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=1050272714.30123.5.camel@localhost \
--to=brad@brad-x.com \
--cc=gentoo-dev@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