On 2006.07.27 10:00, Chris Bainbridge wrote:
On 27/07/06, Stefan Schweizer <[EMAIL PROTECTED]> wrote:
[snip]
As a better system I would like to see packages stable automatically
after 30 days and no bugs. But this is probably not going to happen
with gentoo so I just stay away from stable and put ACCEPT_KEYWORDS
in my make.conf
[snip]
The testing is supposed to be for the ebuild, not the package itself,
so there's not much point in holding back packages with simple
ebuilds from being stabilised. And the testing process isn't that
extensive anyway - all it ensures is that the package builds and can
be run on one particular arch testers system. No disrespect to the
testers, but they can't be experts in every particular piece of
software. How much code coverage does a typical ebuild really get
when being tested?
I'd say no bugs, 30 days, passes internal tests, being run by users
=> stablise, for the majority of packages (obviously, there may be
some exceptions...).
--
gentoo-dev@gentoo.org mailing list
Maybe this semi-automatic stabilisation by default could be adopted by
the tree cleaners project?
Maybe I'll get flamed for even thinking that.
Regards,
Roy Bamford
--
gentoo-dev@gentoo.org mailing list
