release: Propose a shorter release cycle for 2.7.

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 <russell@ovn.org>
Acked-by: Ben Pfaff <blp@ovn.org>

0 files changed, 0 insertions, 0 deletions