There is currently no usable release of FreeBSD.

[Kim Shrier]

On Jun 4, 2014, at 12:18 PM, Tony Li <tony.li at tony.li> wrote:

> 
> What’s the problem with using ‘legacy’?
> 
> Tony
> 
> On Jun 4, 2014, at 9:52 AM, John Kozubik <john at kozubik.com> wrote:
> 
>> 
>> freebsd.org website shows the following:
>> 
>> Production: 10.0
>> Legacy: 9.2, 8.4
>> Upcoming: 9.3
>> 
>> You can't put an x.0 release into production (a bigotry that is *well deserved* in light of 5.0 and 9.0) ... and 9.2 and 8.4 are legacy ... and we all know that 9.3 is as far as the 9 branch is going to go, so that's a dead end for any serious deployment.
>> 
>> Let's pretend for a moment that you are going to use FreeBSD for something other than FreeBSD development.  Let's pretend that you have customers and shareholders and boardmembers and contracts and regulators.
>> 
>> Which version of FreeBSD would you use ?
>> _______________________________________________
>> freebsd-hackers at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
>> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"
> 
> _______________________________________________
> freebsd-hackers at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"

If I was putting together a production system today, I would use 9.2 p7.  When 9.3
comes out, I would upgrade to it after evaluating it.  Even though 9.3 is the end
of the 9.x line, it will still be supported for 3 years after it comes out.

10.0 is a big enough change that I would hold off until 10.2 before using it unless
I needed something in 10 that wasn’t in 9.  I typically hold off until a x.2 release
to put something in production as by that time, there are usually no surprises.

Kim