> On Dec 9, 2014, at 2:30 PM, Mark Haywood <mark.hayw...@oracle.com> wrote: > > On 12/8/14, 2:02 AM, Justin Pettit wrote: >>> On Dec 7, 2014, at 5:44 PM, Mark Haywood <mark.hayw...@oracle.com> wrote: >>> >>> The FAQ says that there are usually several long-term support releases a >>> year. What determines when an LTS is released and when would there be >>> another one taking the place of 2.3.0? >> The LTS releases happen as critical bug fixes are fixed or every few months >> otherwise. We're going to try to introduce more regularity with a new QA >> process that is in the early planning stages. > > So, I think you this means 2.3.1 might be released as bug fixes require or > possibly in a few months as a mechanism to release a collection of > non-critical bug fixes?
Correct. In fact, we already released 2.3.1: http://openvswitch.org/pipermail/announce/2014-December/000071.html >> As for when new LTS branches are chosen, that's less predictable. In the >> past we tried to do them roughly once a year, but we made so many >> fundamental architectural changes between 1.10 and 2.2 that we deliberately >> locked 1.9 as the LTS until 2.3. I don't expect that we'll need to do that >> again, so there should be a more regular cadence between LTSs. > > And this means a new branch, say 2.4 maybe, would possibly be released in > about a year? 2.4 will likely be released early in the first quarter of 2015. However, 2.4 will not be an LTS. Some later version of OVS will be LTS, which will likely be a year or so from now. Put another way, not every "y" in a "x.y.z" version is LTS. --Justin _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss