public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Steve Dibb <beandog@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How packages are made stable
Date: Thu, 04 Jan 2007 14:34:31 -0700	[thread overview]
Message-ID: <459D72E7.1050206@gentoo.org> (raw)
In-Reply-To: <459D686C.7050304@gentoo.org>

Steve Dibb wrote:
> Andrey Gerasimenko wrote:
>> Looking at the Portage tree, I see that some packages are kept ~x86 
>> for long time without any bugs referenced in the changelog or 
>> Bugzilla. How are they being made stable (or where in the docs is the 
>> process described)? 
> They need to be in the tree for at least 30 days, no bugs, and if 
> someone files a stable request ebuild, then an arch tester will test 
> it, and then a dev will keyword it stable.
>
Oh, and I forgot .... all the dependencies should be marked stable as well.

I would actually encourage users to find and file stable request ebuild 
bugs.  Just make sure you post emerge --info along there in the bug.

Steve
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-01-04 21:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-04 20:20 [gentoo-user] How packages are made stable Andrey Gerasimenko
2007-01-04 20:49 ` Steve Dibb
2007-01-04 21:34   ` Steve Dibb [this message]
2007-01-05  8:49   ` Robert Cernansky
2007-01-05 14:04     ` Andrey Gerasimenko
2007-01-05 14:24       ` Robert Cernansky
2007-01-05 14:33       ` Steve Dibb
2007-01-05 16:02         ` Robert Cernansky
2007-01-05 16:24           ` Steve Dibb
2007-01-05 16:28           ` Kevin O'Gorman
2007-01-05 16:58             ` Steve Dibb
2007-01-06  0:06               ` [gentoo-user] How packages are made stable - suggestion for improvement Daevid Vincent
2007-01-06  0:23                 ` Steve Dibb
2007-01-06  1:24                   ` David Relson
2007-01-06 10:49                     ` Andrey Gerasimenko
2007-01-05 14:30     ` [gentoo-user] How packages are made stable Steve Dibb

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=459D72E7.1050206@gentoo.org \
    --to=beandog@gentoo.org \
    --cc=gentoo-user@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