On Fri, 05 Jan 2007 11:49:30 +0300, Robert Cernansky <[EMAIL PROTECTED]>
wrote:
On Thu, 04 Jan 2007 13:49:48 -0700 Steve Dibb <[EMAIL PROTECTED]> 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.
Most stuff doesnt get marked stable mostly because there aren't any
stable requests.
Stabilisation bug it not a requirement. Package should go to stable
after 30 days + no bugs even without stabilization bug. I have an
impresion that developers are _waiting_ for stabilization bugs which
is wrong.
I've raised a similar question few months ago. It's pretty long
discussion on -user and -dev:
http://thread.gmane.org/gmane.linux.gentoo.user/166565/
http://thread.gmane.org/gmane.linux.gentoo.devel/40719/
Robert
Thanks for the threads. My impression is that the way stabilization works
should be described in a place of high visibility, at least in the FAQ. I
beleive this question will be asked again and again if new users do not
see how "stable" is defined early. If they see the definition, no
questions will be asked. For example, I do not think that developers
waiting for bug reports to stabilize an ebuild is either wrong or correct.
It is just a part of the current definition of the term "stable".
--
Andrei Gerasimenko
--
gentoo-user@gentoo.org mailing list
