Date: Sat, 7 Jun 2008 13:39:07 -0700 From: Jo Rhett <jrhett@netconsonance.com> To: Adrian Chadd <adrian@freebsd.org> Cc: FreeBSD Stable <freebsd-stable@freebsd.org>, Chris Marlatt <cmarlatt@rxsec.com> Subject: Re: challenge: end of life for 6.2 is premature with buggy 6.3 Message-ID: <346A79CC-B230-412D-892C-7164774C8954@netconsonance.com> In-Reply-To: <d763ac660806050839y40674b11hdbc54ddbd262bf1c@mail.gmail.com> References: <9B7FE91B-9C2E-4732-866C-930AC6022A40@netconsonance.com> <4846D849.2090005@FreeBSD.org> <4846E14C.709@FreeBSD.org> <AC78CAC0-BA7C-4A20-9BEE-E7E37FD225E7@netconsonance.com> <48472CCF.8080101@FreeBSD.org> <4847EF62.1070709@rxsec.com> <4847F814.10409@FreeBSD.org> <4847FB1D.1050400@rxsec.com> <d763ac660806050812o71329243lc7d58506490bd6b1@mail.gmail.com> <4848073C.2060509@rxsec.com> <d763ac660806050839y40674b11hdbc54ddbd262bf1c@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 5, 2008, at 8:39 AM, Adrian Chadd wrote: > So yes, the way to contribute is to get involved. If you think there's > a real desire to take FreeBSD-6.2 (as an example) and continue > supporting security patches and critical bugfixes, versus the > larger-scale changes which seem to have gone on in /usr/src/sys then > just get together a group, generate some patches and submit them. Splinter groups, in my experience, tend to create duplicate work loads and make things harder, not easier. They seem to be useful only when there is a deadlock in the core team, and so far FreeBSD has avoided that. I would rather focus my efforts on something that produces more effective results. This is the reasoning behind my question: why drop 6.2 and 6.1 at the same time? What is the real cost of supporting 6.2 until a new stable version ships? -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?346A79CC-B230-412D-892C-7164774C8954>