OVS recently adopted a six month release cycle. OVS doesn't have to align to other projects, but it can be beneficial. The dates for OVS 2.6 aligned very well to OpenStack, which is a major consumer of OVS that usually does 6 month releases.
OpenStack is doing a short release cycle for its Ocata release to adjust to changes to their event schedule. https://releases.openstack.org/ocata/schedule.html As a result, I propose that we adjust the schedule for OVS 2.7 to remain just ahead of OpenStack. The specific target dates for 2.7 I propose would be: branch-2.7 created - Jan 11, 2017 2.7.0 released from branch-2.7 - Feb 8, 2017 The key differences are moving the release date from March to February and also shortening the period between branch creation and release to account for the shorter development cycle. This patch also adjusts the release cycle target dates to indicate February as the target release month instead of March. Signed-off-by: Russell Bryant <russ...@ovn.org> --- Documentation/release-process.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/release-process.md b/Documentation/release-process.md index 0f8f49d..fcbd174 100644 --- a/Documentation/release-process.md +++ b/Documentation/release-process.md @@ -88,9 +88,9 @@ of course is subject to change. | Time (months) | Approximate Dates | Event | |---------------|-------------------|--------------------------------------| -| T | Apr 1, Oct 1 | Release cycle for version x.y begins | -| T + 4 | Aug 1, Feb 1 | branch-x.y forks from master | -| T + 5.5 | Sep 15, Mar 15 | branch-x.y released as version x.y.0 | +| T | Mar 1, Sep 1 | Release cycle for version x.y begins | +| T + 4 | Jul 1, Jan 1 | branch-x.y forks from master | +| T + 5.5 | Aug 15, Feb 15 | branch-x.y released as version x.y.0 | Contact ------- -- 2.9.3 _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
