[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [xen staging] docs: add reference to release cycle discussion
commit a58fca51abd46a88d87390fce333c90376e68367 Author: Juergen Gross <jgross@xxxxxxxx> AuthorDate: Mon Jul 11 12:13:40 2022 +0200 Commit: Jan Beulich <jbeulich@xxxxxxxx> CommitDate: Mon Jul 11 12:13:40 2022 +0200 docs: add reference to release cycle discussion As it is coming up basically every release cycle of Xen, add a reference to the discussion why the current release scheme has been selected in the release management documentation. Signed-off-by: Juergen Gross <jgross@xxxxxxxx> Reviewed-by: Henry Wang <Henry.Wang@xxxxxxx> Acked-by: Jan Beulich <jbeulich@xxxxxxxx> --- docs/process/xen-release-management.pandoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/process/xen-release-management.pandoc b/docs/process/xen-release-management.pandoc index b746c7157d..8f80d61d2f 100644 --- a/docs/process/xen-release-management.pandoc +++ b/docs/process/xen-release-management.pandoc @@ -19,6 +19,8 @@ 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 subsequent release cycle would be shortened. +The reasons for this schedule have been discussed on +[xen-devel](https://lists.xen.org/archives/html/xen-devel/2018-07/msg02240.html). 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 -- generated by git-patchbot for /home/xen/git/xen.git#staging
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |