Skip to contentSkip to conversation

docs: add reference to release cycle discussion

PATCH In review Juergen Gross 3 participants 3 messages Jul 8, 2022

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 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.

---
 docs/process/xen-release-management.pandoc | 2 ++
 1 file changed, 2 insertions(+)
docs/process/xen-release-management.pandoc +2 -0
index b746c7157d..8f80d61d2f 100644
@@ -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
Signature · 1 line
2.35.3
Reviewed-by Acked-by on v1 1/1
#1 lore raw

Hi Juergen,

Quoted 8 lines

-----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.

Thanks very much for this information and the change.

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