On 8/27/07, Kevin Cheng <[EMAIL PROTECTED]> wrote: > Artur, > > Thanks, > > Upgrade code based on release of obsd is easy, but it would a big job to > maintain early released of products based on previous version of obsd. For > example, we would maintain 8 version of products from 3.3 to 4.0 if codes > are upgraded every half years.
Why would you maintain support for products going back to vastly unsupported versions of OpenBSD? If I had a product based on OpenBSD, I wouldn't give customers an excuse to keep themselves on older and unsupported releases. Do you want customers running 3.3 right now? They haven't been able to get patches for years now. In my experience at least part of the reason system designers choose OpenBSD as a basis for their solution is the security focus. You go that far out of date, you lose that advantage. Yes, the project has a release schedule. No, that doesn't make it easy to maintain the 5 year life cycle that other platforms like to advertise. It also doesn't mean that their schedule is superior or is even a good idea (or accurate). Some vendors are maintaining "support" for NT4 still; customer demand is driving that. It's stupid, and those that play that game are either really stupid or really good at getting risk acceptance documents signed off on. Or both. DS
