All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bertrand Marquis" <bertrand.marquis@arm.com>
To: Christopher Clark <christopher.w.clark@gmail.com>
Cc: "meta-virtualization@lists.yoctoproject.org"
	<meta-virtualization@lists.yoctoproject.org>,
	"cardoe@gentoo.org" <cardoe@gentoo.org>,
	"bruce.ashfield@gmail.com" <bruce.ashfield@gmail.com>
Subject: Re: [meta-virtualization][PATCH v2 4/6] xen, xen-tools: Document the version update process in README
Date: Thu, 15 Apr 2021 09:21:19 +0000	[thread overview]
Message-ID: <B18934F5-C60A-42D2-898E-26F6AA521B33@arm.com> (raw)
In-Reply-To: <20210414233924.55589-4-christopher.w.clark@gmail.com>

Hi,

> On 15 Apr 2021, at 00:39, Christopher Clark via lists.yoctoproject.org <christopher.w.clark=gmail.com@lists.yoctoproject.org> wrote:
>
> 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>

Cheers
Bertrand

> ---
> recipes-extended/xen/README | 50 +++++++++++++++++++++++++++++++++++++
> 1 file changed, 50 insertions(+)
>
> diff --git a/recipes-extended/xen/README b/recipes-extended/xen/README
> index f286bb5..b9117f0 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
> drop patches in 'recipes-extened/xen/files' and create a bbappend adding those
> patches to SRC_URI and they will be applied. Alternatively, you can override
> the SRC_URI to a git repo you provide that contains the patches.
> +
> +recipe maintenance
> +------------------
> +
> +# Xen version update
> +
> +The following rules shall be followed to define which versions of Xen have
> +recipes in meta-virtualization:
> +
> +- Before a Yocto release meta-virtualization shall have recipes for:
> +    - the latest stable major version of Xen, and
> +
> +    - the current version of the Xen master branch (known as the git recipes)
> +
> +    - In addition, there may also be recipes included for the previous stable
> +      major version of Xen, in the case where the latest stable major version
> +      is new and the prior stable major version of Xen is to be the preferred
> +      version for the Yocto release
> +
> +- On Yocto LTS and the latest stable Yocto release branch, the preferred Xen
> +  major version that is present when the Yocto release is issued must stay
> +  supported and the recipes shall be regularly updated to follow updates
> +  available in the Xen stable branch for that Xen major release.
> +
> +- On Yocto LTS and the latest stable Yocto release branch, the recipes for the
> +  latest Xen major version shall also be regularly updated to follow updates
> +  available in the Xen stable branch for that Xen major release.
> +
> +- On the master / in-development Yocto branch, new Xen recipes shall be added
> +  when there is a new Xen major release.
> +
> +    - depending on the timing of the next Yocto release, the new recipes may
> +      be preferred, or the prior major version recipes may remain preferred
> +      until after the Yocto release
> +
> +    - the recipes for the previous Xen stable major version shall be removed
> +      from the branch when it is no longer the preferred Xen version
> +
> +- On Yocto LTS and the latest stable Yocto release branch, new Xen recipes
> +  shall be added when there is a new Xen major release.
> +
> +    - The preferred version of the Xen recipes shall always stay at the same
> +      Xen major version once a Yocto release has been issued, and shall receive
> +      regular updates to track the stable Xen branch of that Xen release.
> +
> +    - When new Xen recipes are added to a Yocto branch for a new Xen major
> +      version, then any older Xen recipes present, except for the original
> +      preferred version recipes, shall be marked as not updated anymore by
> +      adding a comment inside the recipes. The older recipes will not receive
> +      any build tests or be updated to follow the Xen branch.
> --
> 2.25.1
>
>
> 
>

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

  reply	other threads:[~2021-04-15  9:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-14 23:39 [meta-virtualization][PATCH v2 1/6] xen-tools: fix 32-bit x86 build by setting pvshim configure flags Christopher Clark
2021-04-14 23:39 ` [meta-virtualization][PATCH v2 2/6] xen, xen-tools: add recipes for new stable Xen 4.15 release Christopher Clark
2021-04-15  9:12   ` Bertrand Marquis
2021-04-15 19:24     ` Christopher Clark
2021-04-16  2:24       ` Bruce Ashfield
2021-04-16  6:18         ` Christopher Clark
2021-04-16  9:41           ` Bertrand Marquis
2021-04-16  9:40         ` Bertrand Marquis
2021-04-14 23:39 ` [meta-virtualization][PATCH v2 3/6] xen, xen-tools: uprev git recipes after " Christopher Clark
2021-04-15  9:20   ` Bertrand Marquis
2021-04-14 23:39 ` [meta-virtualization][PATCH v2 4/6] xen, xen-tools: Document the version update process in README Christopher Clark
2021-04-15  9:21   ` Bertrand Marquis [this message]
2021-04-14 23:39 ` [meta-virtualization][PATCH v2 5/6] xtf: introduce recipe for the Xen Test Framework Christopher Clark
2021-04-15  9:54   ` Bertrand Marquis
2021-04-14 23:39 ` [meta-virtualization][PATCH v2 6/6] xtf-image: add a new image " Christopher Clark
2021-04-15  9:54   ` Bertrand Marquis
2021-04-15  9:19 ` [meta-virtualization][PATCH v2 1/6] xen-tools: fix 32-bit x86 build by setting pvshim configure flags Bertrand Marquis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=B18934F5-C60A-42D2-898E-26F6AA521B33@arm.com \
    --to=bertrand.marquis@arm.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=cardoe@gentoo.org \
    --cc=christopher.w.clark@gmail.com \
    --cc=meta-virtualization@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.