[PATCH] xen-release-management doc: More info on schedule

Ian Jackson posted 1 patch 3 years, 2 months ago
Test gitlab-ci passed
Patches applied successfully (tree, apply log)
git fetch https://gitlab.com/xen-project/patchew/xen tags/patchew/20210128163538.13922-1-iwj@xenproject.org
docs/process/xen-release-management.pandoc | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)
[PATCH] xen-release-management doc: More info on schedule
Posted by Ian Jackson 3 years, 2 months ago
This documents our practice, established in 2018
  https://lists.xen.org/archives/html/xen-devel/2018-07/msg02240.html
et seq

CC: Jürgen Groß <jgross@suse.com>
CC: Paul Durrant <xadimgnik@gmail.com>
CC: Wei Liu <wl@xen.org>
Signed-off-by: Ian Jackson <iwj@xenproject.org>
---
 docs/process/xen-release-management.pandoc | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

diff --git a/docs/process/xen-release-management.pandoc b/docs/process/xen-release-management.pandoc
index e1aa1eda8f..a5d70fed67 100644
--- a/docs/process/xen-release-management.pandoc
+++ b/docs/process/xen-release-management.pandoc
@@ -15,8 +15,10 @@ that they can have an idea what to expect from the Release Manager.
 
 # Xen release cycle
 
-The Xen hypervisor project now releases every 8 months. The actual release date
-depends on a lot of factors.
+The Xen hypervisor project now releases every 8 months.  We aim to
+release in the first half of March/July/November.  These dates have
+been chosen to avoid major holidays and cultural events; if one
+release slips, ideally the previous release cycle would be shortened.
 
 We can roughly divide one release into two periods. The development period
 and the freeze period. The former is 6 months long and the latter is about 2
@@ -33,6 +35,12 @@ 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.
 
+The precise release schedule depends on a lot of factors and needs to
+be set afresh by the Release Manager in each release cycle.  When the
+release is in March, particular consideration should be given to the
+Chinese New Year holidaty which will then typically occur curing the
+freeze, so the freeze should probably be extended to compensate.
+
 # The different roles in a Xen release
 
 ## Release Manager
-- 
2.20.1


Re: [PATCH] xen-release-management doc: More info on schedule
Posted by Jan Beulich 3 years, 2 months ago
On 28.01.2021 17:35, Ian Jackson wrote:
> This documents our practice, established in 2018
>   https://lists.xen.org/archives/html/xen-devel/2018-07/msg02240.html
> et seq
> 
> CC: Jürgen Groß <jgross@suse.com>
> CC: Paul Durrant <xadimgnik@gmail.com>
> CC: Wei Liu <wl@xen.org>
> Signed-off-by: Ian Jackson <iwj@xenproject.org>
> ---
>  docs/process/xen-release-management.pandoc | 12 ++++++++++--
>  1 file changed, 10 insertions(+), 2 deletions(-)
> 
> diff --git a/docs/process/xen-release-management.pandoc b/docs/process/xen-release-management.pandoc
> index e1aa1eda8f..a5d70fed67 100644
> --- a/docs/process/xen-release-management.pandoc
> +++ b/docs/process/xen-release-management.pandoc
> @@ -15,8 +15,10 @@ that they can have an idea what to expect from the Release Manager.
>  
>  # Xen release cycle
>  
> -The Xen hypervisor project now releases every 8 months. The actual release date
> -depends on a lot of factors.
> +The Xen hypervisor project now releases every 8 months.  We aim to
> +release in the first half of March/July/November.  These dates have
> +been chosen to avoid major holidays and cultural events; if one
> +release slips, ideally the previous release cycle would be shortened.

s/previous/subsequent/ ?

> @@ -33,6 +35,12 @@ 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.
>  
> +The precise release schedule depends on a lot of factors and needs to
> +be set afresh by the Release Manager in each release cycle.  When the
> +release is in March, particular consideration should be given to the
> +Chinese New Year holidaty which will then typically occur curing the
> +freeze, so the freeze should probably be extended to compensate.

s/curing/during/ I suppose, and there's a stray t in "holiday".

Lgtm apart from these - feel free to translate to an ack if you
think one is needed.

Jan

Re: [PATCH] xen-release-management doc: More info on schedule
Posted by Ian Jackson 3 years, 2 months ago
Jan Beulich writes ("Re: [PATCH] xen-release-management doc: More info on schedule"):
> On 28.01.2021 17:35, Ian Jackson wrote:
> > -The Xen hypervisor project now releases every 8 months. The actual release date
> > -depends on a lot of factors.
> > +The Xen hypervisor project now releases every 8 months.  We aim to
> > +release in the first half of March/July/November.  These dates have
> > +been chosen to avoid major holidays and cultural events; if one
> > +release slips, ideally the previous release cycle would be shortened.
> 
> s/previous/subsequent/ ?

No, we should go back in time and retrospectively not have slipped
after all :-).

> Lgtm apart from these - feel free to translate to an ack if you
> think one is needed.

Thanks for the review.  I have put your ack on it indeed and will push
it in a moment.

Ian.