From: Jon Portnoy <avenj@gentoo.org>
To: Rainer Groesslinger <rainer.groesslinger@gmx.net>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Is there a process for marking ebuilds stable?
Date: Sun, 13 Apr 2003 19:07:37 -0400 [thread overview]
Message-ID: <20030413230737.GA18713@cerberus.oppresses.us> (raw)
In-Reply-To: <200304140100.51467.rainer.groesslinger@gmx.net>
On Mon, Apr 14, 2003 at 01:00:51AM +0200, Rainer Groesslinger wrote:
> On Monday 14 April 2003 00:25, Brad Laue wrote:
> > 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.
>
> correct, same here.
> Additionally there are many ebuilds in the tree that should be removed
> again...for example most of the game mods (not because I don't like gamers
> just because e.g. osp for quake3 isn't maintained although quite some time
> passed already since the last osp release(s) and in a multiplayer game it's
> useless to have an old version of something ;)
Submit an updated ebuild.
>
> > 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.
>
> Problem: Gentoo doesn't have maintainers !
> It has been discussed to introduce a MAINTAINER="xxxx@gentoo.org" thing in the
> ebuilds but it seems like the idea got dropped by the core developers (or
> didn't even get attention, I don't know).
>
> The only real maintainer is carpaski for portage, most other packages are
> worked on by more or less "Freelancers"...
> Sure, many people are related to something, but you can't see who is the
> maintainer of a certain package.
> Just imagine...there are some packages where version 0.1 was submitted by dev
> A, 0.2 by dev B and 0.2.1 by dev C and 0.3 again by dev B etc.
>
Read changelogs.
> Not, that this is bad at all, but it would be much better to have "real"
> maintainers like almost every other distribution has, too.
We have real maintainers. For example, I maintain a handful of packages.
Could you be more specific about what constitutes a "real" 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.
>
> stable.gentoo.org is _great_ ! Thanks so much to blizzy (unfortunatly he's not
> in the dev team any more). The problem here is that this site must be pushed
> quite hard because there are packages in the tree only a few people use and
> if those people don't use stable.gentoo.org they won't be stable anytime soon
> or might - in a bad case - be pushed into stable because nobody complain
> although it's just because nobody uses stable.gentoo.org
>
--
Jon Portnoy
avenj/irc.freenode.net
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-04-13 23:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-13 22:25 [gentoo-dev] Is there a process for marking ebuilds stable? Brad Laue
2003-04-13 23:00 ` Rainer Groesslinger
2003-04-13 23:07 ` Rainer Groesslinger
2003-04-13 23:07 ` Jon Portnoy [this message]
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=20030413230737.GA18713@cerberus.oppresses.us \
--to=avenj@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=rainer.groesslinger@gmx.net \
/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