All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wl@xen.org>
To: Xen Development List <xen-devel@lists.xenproject.org>
Cc: Juergen Gross <jgross@suse.com>,
	Lars Kurth <lars.kurth@citrix.com>,
	committers@xenproject.org, Wei Liu <wl@xen.org>
Subject: [Xen-devel] [PATCH for-4.13] docs: adjust xen release cycle text
Date: Fri, 15 Nov 2019 14:27:20 +0000	[thread overview]
Message-ID: <20191115142720.5588-1-wl@xen.org> (raw)

Fix text about release cycle. Drop the conjured up example that's no
longer applicable.

Signed-off-by: Wei Liu <wl@xen.org>
---
 docs/process/xen-release-management.pandoc | 15 +++------------
 1 file changed, 3 insertions(+), 12 deletions(-)

diff --git a/docs/process/xen-release-management.pandoc b/docs/process/xen-release-management.pandoc
index d6abc90a02..e1aa1eda8f 100644
--- a/docs/process/xen-release-management.pandoc
+++ b/docs/process/xen-release-management.pandoc
@@ -15,12 +15,11 @@ that they can have an idea what to expect from the Release Manager.
 
 # Xen release cycle
 
-The Xen hypervisor project now releases twice a year, at the beginning of
-June and the beginning of December. The actual release date depends on a lot
-of factors.
+The Xen hypervisor project now releases every 8 months. The actual release date
+depends on a lot of factors.
 
 We can roughly divide one release into two periods. The development period
-and the freeze period. The former is 4 months long and the latter is about 2
+and the freeze period. The former is 6 months long and the latter is about 2
 months long.
 
 During development period, contributors submit patches to be reviewed and
@@ -34,14 +33,6 @@ During freeze period, the tree is closed for new features. Only bug fixes are
 accepted. This period can be shorter or longer than 2 months. If it ends up
 longer than 2 months, it eats into the next development period.
 
-Here is a conjured up example (use ```cal 2017``` to get an idea):
-
-* Development period: 2017 June 11 - 2017 September 29
-    * the "cut-off date" is 2017 September 29
-    * the "last posting date" is 2017 September 15
-* Freeze period: 2017 October 2 - 2017 December 7
-    * the anticipated release date is 2017 December 7
-
 # The different roles in a Xen release
 
 ## Release Manager
-- 
2.20.1


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

             reply	other threads:[~2019-11-15 14:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15 14:27 Wei Liu [this message]
2019-11-15 14:43 ` [Xen-devel] [PATCH for-4.13] docs: adjust xen release cycle text Jürgen Groß
2019-11-15 14:44 ` Jan Beulich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191115142720.5588-1-wl@xen.org \
    --to=wl@xen.org \
    --cc=committers@xenproject.org \
    --cc=jgross@suse.com \
    --cc=lars.kurth@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.