Date: Wed, 18 Jan 2012 13:34:22 -0800 From: Xin Li <delphij@delphij.net> To: CeDeROM <cederom@tlen.pl> Cc: d@delphij.net, freebsd-bugs@freebsd.org, delphij@freebsd.org Subject: Re: misc/164290: FreeBSD 9.0 IS NOT YET PRODUCTION/STABLE Message-ID: <4F173ADE.5030606@delphij.net> In-Reply-To: <CAFYkXj=s_bOqEjxitGLz-cXMsebWaNqtRS2B2=ST4EzKk4oc3w@mail.gmail.com> References: <201201182118.q0ILIYaq079339@freefall.freebsd.org> <CAFYkXj=s_bOqEjxitGLz-cXMsebWaNqtRS2B2=ST4EzKk4oc3w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/18/12 13:26, CeDeROM wrote: > On Wed, Jan 18, 2012 at 9:18 PM, <delphij@freebsd.org> wrote: >> Synopsis: FreeBSD 9.0 IS NOT YET PRODUCTION/STABLE I'm closing >> this PR because it does not contain any details about the >> hardware nor have any proposal about how to deal with the >> problem. >> >> Please, become an active participant of the project by >> downloading and testing the images when we are doing BETA and >> RCs, and shout out loudly if you hit some bugs and these problems >> gets addressed. >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=164290 > > Then simply call for testing, work more on making it stable, and > when its stable mark it stable. The logical consequence of > releasing And that's not a PR system for. Filling PR system with invalid requests does not benefit anyone. > unstable as production is to lie to users. New people that install > 9.0 release/stable that even won't install will never look at this > system again, the changes instroduced in 9.0 makes even me want to > switch to another os :-( Let me put this straight: a release with some defect in time is better than a release with defect and significant delay. We use FreeBSD in our products and we found a bug that we thought is very serious that must be fixed before release and guess what? There are very few complains about it in the mailing list and everybody is convinced that we should go ahead with release, and we end up patching it in our own product by back-porting. This type of issue can only be avoided if users are active participant to the project, it's VERY important to make more people *know* what's going wrong before the release. Cheers, - -- Xin LI <delphij@delphij.net> https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8XOt4ACgkQOfuToMruuMCQIgCbBn6pdtvaQVVTDuWjJCmQt5QI 4UIAnjrLY0hqHEOnmh3CdJgd9VYD3dXH =/lBW -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F173ADE.5030606>