Date: Mon, 23 Feb 2009 15:48:47 -0800 From: prad <prad@towardsfreedom.com> To: freebsd-questions@freebsd.org Subject: Re: understanding freebsd development logic Message-ID: <20090223154847.39df6edc@gom.home> In-Reply-To: <87d4d8rd5g.fsf@kobe.laptop> References: <20090223142559.3c5ff9e9@gom.home> <87d4d8rd5g.fsf@kobe.laptop>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 24 Feb 2009 00:39:39 +0200
Giorgos Keramidas <keramida@ceid.upatras.gr> wrote:
> The thesis of Niklas Saers is a bit dated now, but it is a wonderful
> document and it answers this question (including a few others too).
>
> I think it will be an interesting read for you:
>
most certainly!!
i've been going through it quickly and it is really fascinating to see
the historical structure and the development models.
specifically, this would seem to answer much:
"The project provides multiple versions of FreeBSD intended for
audiences with different priorities between the newest features and
rock solid stability and security. This means that the newest minor
release or updates along a security branch are already old in terms of
being well tested when they are released."
and coordinates well with things some of the other posters to this
thread have written.
i rather like this approach because it doesn't let the old stuff just
die (in fact, we just installed 4.4 on some of our machines) and the
idea of backporting is really quite a remarkable concept.
i will look at niklas' thesis in greater detail over the next few days,
so thank you very much for drawing my attention to it.
--
In friendship,
prad
... with you on your journey
Towards Freedom
http://www.towardsfreedom.com (website)
Information, Inspiration, Imagination - truly a site for soaring I's
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090223154847.39df6edc>