Message ID | 20220708041258.10349-1-jgross@suse.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | docs: add reference to release cycle discussion | expand |
Hi Juergen, > -----Original Message----- > Subject: [PATCH] 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@suse.com> Thanks very much for this information and the change. Reviewed-by: Henry Wang <Henry.Wang@arm.com> Acked-by: Henry Wang <Henry.Wang@arm.com> Also btw, I have posted a proposal for the Xen 4.17 release [1], we can start the discussion there. [1] https://lore.kernel.org/xen-devel/AS8PR08MB7991145C8063D6939AFFED8F92829@AS8PR08MB7991.eurprd08.prod.outlook.com/ Kind regards, Henry
On 08.07.2022 06:12, Juergen Gross wrote: > 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@suse.com> Acked-by: Jan Beulich <jbeulich@suse.com>
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
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@suse.com> --- docs/process/xen-release-management.pandoc | 2 ++ 1 file changed, 2 insertions(+)