challenge: end of life for 6.2 is premature with buggy 6.3

[Jo Rhett]

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