From: Sai.Sathujoda@toshiba-tsip.com
To: cip-dev@lists.cip-project.org, jan.kiszka@siemens.com
Cc: Sai <Sai.Sathujoda@toshiba-tsip.com>,
dinesh.kumar@toshiba-tsip.com, kazuhiro3.hayashi@toshiba.co.jp
Subject: [isar-cip-core 2/2] README_version-release-policy.md: Add product description details
Date: Fri, 1 Sep 2023 13:49:43 +0530 [thread overview]
Message-ID: <20230901081943.1816811-2-Sai.Sathujoda@toshiba-tsip.com> (raw)
In-Reply-To: <20230901081943.1816811-1-Sai.Sathujoda@toshiba-tsip.com>
From: Sai <Sai.Sathujoda@toshiba-tsip.com>
The Debian releases, Kernel versions and image features supported
for repsective isar-cip-core release information is added.
Signed-off-by: Sai <Sai.Sathujoda@toshiba-tsip.com>
---
doc/README_version-release-policy.md | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/doc/README_version-release-policy.md b/doc/README_version-release-policy.md
index 918e77a..f8dde38 100644
--- a/doc/README_version-release-policy.md
+++ b/doc/README_version-release-policy.md
@@ -4,6 +4,7 @@
1. [Objective](#objective)
2. [Versioning system](#versioningsystem)
3. [Release policy](#releasepolicy)
+4. [Product Description for metadata release](#productdescription)
## Objective <a name="objective"></a>
@@ -28,3 +29,10 @@ The isar-cip-core metadata follows semantic versioning system i.e **x.y.z** form
An approximate time gap of 3 months is taken between consecutive regular releases. During every release, CIP-Core plans to give out recipes (isar-cip-core metadata) using which the user can build the flavor of their choice.
All the releases can be found [here](https://gitlab.com/cip-project/cip-core/isar-cip-core/-/tags).
+
+## Product Description for metadata release <a name="productdescription></a>"
+
+| **Metadata version** | **Supported Debian versions** | **Supported Kernel versions** | **Features** |
+| -------------------- | --------------------------------| ---------------------------------------------| --------------------------------- |
+| v1.0 | Buster <br> Bullseye | 4.4.x-cip <br> 4.19.x-cip <br> 5.10.x-cip <br> 6.1.x-mainline | Flashable image <br> Security extensions <br> Testing extensions <br> SWupdate support for root partition <br> Secure boot <br> Encryption of data partitions |
+| v1.1 | Buster <br> Bullseye <br> Bookworm | 4.4.x-cip <br> 4.19.x-cip <br> 5.10.x-cip <br> 6.1.x-cip | Flashable image <br> Security extensions <br> Testing extensions <br> SWupdate support for root partition <br> Secure boot <br> Encryption of data partitions |
--
2.30.2
next prev parent reply other threads:[~2023-09-01 8:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 8:19 [isar-cip-core 1/2] README_version-release-policy.md: Rectify "y" incremental details in metadata version Sai.Sathujoda
2023-09-01 8:19 ` Sai.Sathujoda [this message]
2023-09-01 10:39 ` [isar-cip-core 2/2] README_version-release-policy.md: Add product description details Jan Kiszka
2023-10-26 8:56 ` Sai.Sathujoda
2023-10-26 10:06 ` Sai.Sathujoda
2023-10-26 10:17 ` Jan Kiszka
2023-09-01 10:39 ` [isar-cip-core 1/2] README_version-release-policy.md: Rectify "y" incremental details in metadata version Jan Kiszka
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=20230901081943.1816811-2-Sai.Sathujoda@toshiba-tsip.com \
--to=sai.sathujoda@toshiba-tsip.com \
--cc=cip-dev@lists.cip-project.org \
--cc=dinesh.kumar@toshiba-tsip.com \
--cc=jan.kiszka@siemens.com \
--cc=kazuhiro3.hayashi@toshiba.co.jp \
/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.