On Fri, 27 Mar 2009 03:36:41 +0500 Mike Kazantsev <mike_kazant...@fraggod.net> wrote:
> On Thu, 26 Mar 2009 19:13:38 -0300 > Jorge Morais <please.no.spam.h...@gmail.com> wrote: > > > If you had upgraded because of a needed feature, I assume you would > > have read about the release, and thus would know about Tuz. > > So you upgraded to a ~arch kernel without any need. > > Why? > > The question is probably not adressed to me, but... > > It's still a way to check out these new features hands-on :) It's a kernel. > > And while it's ~arch on gentoo, it's actually marked 'stable' by > developers, and, since gentoo ebuild does pretty much nothing but > unpacking it, it should be pretty much as stable as any non-~arch > package. > Even if it already released, it has a higher chance of bugs than a more established kernel. Waiting for the package to become stable on Gentoo is not just about ebuild bugs; it is also about waiting for enough users in general to test the upstream package, and Gentoo users in particular to test the package within Gentoo. And I don't know about the usual quality of brand new Linux releases, but in general, I believe upstream developers want to release early (to get testers and updated contributions), while a distribution may wait until the software is ready and tested. Of course, if you want to actively help, that is a reason to test the latest software... but I am afraid that a kernel bug could lead to unpredictable behavior, data loss and other problems I can't tolerate. Also, I think a kernel has a higher chance of hidden bugs (bugs that don't stand in your face). I think that if you want to contribute as a tester it is easier to test a beta version of mplayer or Firefox (backup your bookmarks!), for example, where bugs are more visible and likely less harmful. Cheers, Jorge -- Software is like sex: it is better when it is free. --Linus Torvalds