From: Chris Gianelloni <wolf31o2@gentoo.org>
To: Paulo Jorge de Oliveira Cantante de Matos <pocm@netvisao.pt>
Cc: Gentoo Dev ML <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Ebuilds from bugs -> portage unstable -> portage stable
Date: Tue, 21 Oct 2003 08:58:27 -0400 [thread overview]
Message-ID: <1066741107.6139.43.camel@localhost> (raw)
In-Reply-To: <1066648576.2398.13.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 999 bytes --]
On Mon, 2003-10-20 at 21:48, Paulo Jorge de Oliveira Cantante de Matos
wrote:
> Hi all,
>
> I'd like to know more about how an ebuild that shows up in
> bugs.gentoo.org goes to portage as unstable and then passes to stable.
> Which are the requirements of each of these phases?
>
> Best regards,
Well, generally the ebuild goes to the developer(s) whom would probably
end up being responsible for the ebuild. For example, if you posted an
ebuild for a game, the Gentoo Games Team would get the bug. One of the
team would take the ebuild and test it. If the ebuild syntax looks
good, then we would add it to portage as ~arch for the architectures we
can test. If after an unspecified period of time (usually 30-90 days)
there are no outstanding bugs for the ebuild, it then gets changed to
stable.
I know that doesn't cover every case, but that is the general way it
works.
--
Chris Gianelloni
Developer, Gentoo Linux
Games Team
Is your power animal a pengiun?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-10-21 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 1:48 [gentoo-dev] Ebuilds from bugs -> portage unstable -> portage stable Paulo Jorge de Oliveira Cantante de Matos
2003-10-21 12:58 ` Chris Gianelloni [this message]
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=1066741107.6139.43.camel@localhost \
--to=wolf31o2@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=pocm@netvisao.pt \
/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