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.  Propose earlier
dates for OVS 2.7 that keep OVS releasing just ahead of OpenStack.

This patch also proposes creating the release branch 4 weeks ahead of
the release instead of 6 to help lessen the impact of the shorter
release cycle.

https://releases.openstack.org/ocata/schedule.html

Signed-off-by: Russell Bryant <russ...@ovn.org>
---
 Documentation/release-process.md | 26 ++++++++++++++++++--------
 1 file changed, 18 insertions(+), 8 deletions(-)

diff --git a/Documentation/release-process.md b/Documentation/release-process.md
index 0f8f49d..0c53812 100644
--- a/Documentation/release-process.md
+++ b/Documentation/release-process.md
@@ -83,14 +83,24 @@ NEWS with an unspecified date.
 Release Scheduling
 ------------------
 
-Open vSwitch makes releases at the following six-month cadence, which
-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 |
+Open vSwitch makes releases at approximately a six-month cadence.
+Specific dates are chosen as a target for each release and may vary
+from exactly six months if deemed appropriate, such as to help
+align with other projects related to Open vSwitch.
+
+In addition to a target release date, each release cycle also has a branch
+creation target date.  Once a release branch has been created, the bar is
+raised on what can be merged for that release.  Prior to the release,
+additional features may be merged, but generally only things that were
+already in progress and targeted at that release.
+
+The following table identifies the planned dates for upcoming release
+milestones.
+
+| Release Milestone              | Approximate Date  |
+| ------------------------------ | ----------------- |
+| branch-2.7 created             | Jan 11, 2017      |
+| 2.7.0 released from branch-2.7 | Feb 8, 2017       |
 
 Contact
 -------
-- 
2.9.3

_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Reply via email to