summaryrefslogtreecommitdiffstats
path: root/recipes-extended
diff options
context:
space:
mode:
authorChristopher Clark <christopher.w.clark@gmail.com>2021-04-16 11:41:34 -0700
committerBruce Ashfield <bruce.ashfield@gmail.com>2021-04-18 20:19:28 -0400
commite9bda61a3dac0f98943ec6193f7d3e37a7779c6c (patch)
tree65a057b192c9e2ebfd9ae5a5df10048c5952b0aa /recipes-extended
parent935223e07fa0a76b17dd0611a78af41785dd8e32 (diff)
downloadmeta-virtualization-e9bda61a3dac0f98943ec6193f7d3e37a7779c6c.tar.gz
xen, xen-tools: Document the version update process in README
Describes the versions of Xen to be included in meta-virtualization and recipe maintenance in release branches. Signed-off-by: Christopher Clark <christopher.w.clark@gmail.com> Reviewed-by: Bertrand Marquis <bertrand.marquis@arm.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Diffstat (limited to 'recipes-extended')
-rw-r--r--recipes-extended/xen/README50
1 files changed, 50 insertions, 0 deletions
diff --git a/recipes-extended/xen/README b/recipes-extended/xen/README
index f286bb54..b9117f0c 100644
--- a/recipes-extended/xen/README
+++ b/recipes-extended/xen/README
@@ -36,3 +36,53 @@ as XSAs (http://xenbits.xen.org/xsa/). The easiest way to include those is to
36drop patches in 'recipes-extened/xen/files' and create a bbappend adding those 36drop patches in 'recipes-extened/xen/files' and create a bbappend adding those
37patches to SRC_URI and they will be applied. Alternatively, you can override 37patches to SRC_URI and they will be applied. Alternatively, you can override
38the SRC_URI to a git repo you provide that contains the patches. 38the SRC_URI to a git repo you provide that contains the patches.
39
40recipe maintenance
41------------------
42
43# Xen version update
44
45The following rules shall be followed to define which versions of Xen have
46recipes in meta-virtualization:
47
48- Before a Yocto release meta-virtualization shall have recipes for:
49 - the latest stable major version of Xen, and
50
51 - the current version of the Xen master branch (known as the git recipes)
52
53 - In addition, there may also be recipes included for the previous stable
54 major version of Xen, in the case where the latest stable major version
55 is new and the prior stable major version of Xen is to be the preferred
56 version for the Yocto release
57
58- On Yocto LTS and the latest stable Yocto release branch, the preferred Xen
59 major version that is present when the Yocto release is issued must stay
60 supported and the recipes shall be regularly updated to follow updates
61 available in the Xen stable branch for that Xen major release.
62
63- On Yocto LTS and the latest stable Yocto release branch, the recipes for the
64 latest Xen major version shall also be regularly updated to follow updates
65 available in the Xen stable branch for that Xen major release.
66
67- On the master / in-development Yocto branch, new Xen recipes shall be added
68 when there is a new Xen major release.
69
70 - depending on the timing of the next Yocto release, the new recipes may
71 be preferred, or the prior major version recipes may remain preferred
72 until after the Yocto release
73
74 - the recipes for the previous Xen stable major version shall be removed
75 from the branch when it is no longer the preferred Xen version
76
77- On Yocto LTS and the latest stable Yocto release branch, new Xen recipes
78 shall be added when there is a new Xen major release.
79
80 - The preferred version of the Xen recipes shall always stay at the same
81 Xen major version once a Yocto release has been issued, and shall receive
82 regular updates to track the stable Xen branch of that Xen release.
83
84 - When new Xen recipes are added to a Yocto branch for a new Xen major
85 version, then any older Xen recipes present, except for the original
86 preferred version recipes, shall be marked as not updated anymore by
87 adding a comment inside the recipes. The older recipes will not receive
88 any build tests or be updated to follow the Xen branch.