Date: Thu, 11 Oct 2007 01:58:51 +0200 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-current@freebsd.org Subject: Re: suggest renaming and extending the -CURRENT and -STABLE lines Message-ID: <fejovs$lj8$1@sea.gmane.org> In-Reply-To: <20071010231643.GF58929@over-yonder.net> References: <feilee$2m3t$3@nermal.rz1.convenimus.net> <86przndoe8.fsf@ds4.des.no> <feir48$ah4$1@sea.gmane.org> <20071010231643.GF58929@over-yonder.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig0CF52214415F0637A3158BF8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Matthew D. Fuller wrote: > On Wed, Oct 10, 2007 at 05:29:12PM +0200 I heard the voice of > Ivan Voras, and lo! it spake thus: >> And we'll find many other people on this newsgroup who do the same, >> but not everyone's a kernel hacker, or even a decent programmer, so >> it's kind of insignificant. >=20 > I'm not a kernel hacker, and I don't remember the last time I ran a > production system on a release longer than it took to do a buildworld, > going back to 2.1.x. My workstation runs -CURRENT, though I rarely > run -CURRENT on other production systems (rarely !=3D never, but it is > rare). Unfortunately (for this developer-centric practice), the trend in large and/or important production environments is - as seen in Linux (and Solaris) - to severely limit major OS upgrades. Of course the existing possibility to do is excellent, but more and more end-users, especially big ones, are going with big Linux distributions that basically stay frozen (except for security upgrades) for years. And this idea gets a +1 from me - productions releases that are expected to run for years should be able to "just work" without upgrading to the "kernel of the week". To do this, a stable anchor-point is required and that's what -RELEASEes should be for. I think the fact that not all our -RELEASES are created equal (some are "extended support" releases) should be more advertised and explained. --------------enig0CF52214415F0637A3158BF8 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHDWc7ldnAQVacBcgRAq0hAJ0d2UnljgQzZGFFgI2yEAgtMOeEhgCgiUdI acnTUxwg/Hfk5CSBz7Uu14s= =ruxS -----END PGP SIGNATURE----- --------------enig0CF52214415F0637A3158BF8--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fejovs$lj8$1>