| Message ID | 20230901081943.1816811-2-Sai.Sathujoda@toshiba-tsip.com (mailing list archive) |
|---|---|
| State | Rejected |
| Headers | show |
| Series | [isar-cip-core,1/2] README_version-release-policy.md: Rectify "y" incremental details in metadata version | expand |
On 01.09.23 10:19, Sai.Sathujoda@toshiba-tsip.com wrote: > 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. respective > > 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) We are not building products in the CIP project. > > ## 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 | This is like a mini changelog, in addition to the full changelog (git history) and the release summaries. What is the purpose if this table, who is expected to read that? Jan
Hi Jan, We are thinking that this description table will help in Configuration management as well as in future where one can refer this to know the features for specific release. This will help to create images of their choice. E.g. version v1.1 meta-data is used to create evaluation images with some specific features which might have been deprecated in future point of time. Later when someone in future wants to generate an image with those specific features, then the information in this table will help. Please provide your opinion, Jan. Thanks and Regards, Sai Ashrith. -----Original Message----- From: Jan Kiszka <jan.kiszka@siemens.com> Sent: Friday, September 1, 2023 4:10 PM To: ashrith sai(ＴＳＩＰ) <Sai.Sathujoda@toshiba-tsip.com>; cip-dev@lists.cip-project.org Cc: dinesh kumar(ＴＳＩＰ TMIEC ODG Porting) <dinesh.kumar@toshiba-tsip.com>; hayashi kazuhiro(林 和宏 ＤＭＥ ○ＤＩＧ□ＭＰＳ○ＭＰ４) <kazuhiro3.hayashi@toshiba.co.jp> Subject: Re: [isar-cip-core 2/2] README_version-release-policy.md: Add product description details On 01.09.23 10:19, Sai.Sathujoda@toshiba-tsip.com wrote: > 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. respective > > 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) We are not building products in the CIP project. > > ## 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 | This is like a mini changelog, in addition to the full changelog (git history) and the release summaries. What is the purpose if this table, who is expected to read that? Jan -- Siemens AG, Technology Linux Expert Center
Hi Jan, Since we did not get a chance to discuss this point in last few CIP core meetings, we are discussing this over mail to avoid any further delay. Thanks and Regards, Sai Ashrith ( T S I P ) -----Original Message----- From: ashrith sai(ＴＳＩＰ) Sent: Thursday, October 26, 2023 2:27 PM To: Jan Kiszka <jan.kiszka@siemens.com>; cip-dev@lists.cip-project.org Cc: dinesh kumar(ＴＳＩＰ TMIEC ODG Porting) <dinesh.kumar@toshiba-tsip.com>; hayashi kazuhiro(林 和宏 ＤＭＥ ○ＤＩＧ□ＭＰＳ○ＭＰ４) <kazuhiro3.hayashi@toshiba.co.jp> Subject: RE: [isar-cip-core 2/2] README_version-release-policy.md: Add product description details Hi Jan, We are thinking that this description table will help in Configuration management as well as in future where one can refer this to know the features for specific release. This will help to create images of their choice. E.g. version v1.1 meta-data is used to create evaluation images with some specific features which might have been deprecated in future point of time. Later when someone in future wants to generate an image with those specific features, then the information in this table will help. Please provide your opinion, Jan. Thanks and Regards, Sai Ashrith. -----Original Message----- From: Jan Kiszka <jan.kiszka@siemens.com> Sent: Friday, September 1, 2023 4:10 PM To: ashrith sai(ＴＳＩＰ) <Sai.Sathujoda@toshiba-tsip.com>; cip-dev@lists.cip-project.org Cc: dinesh kumar(ＴＳＩＰ TMIEC ODG Porting) <dinesh.kumar@toshiba-tsip.com>; hayashi kazuhiro(林 和宏 ＤＭＥ ○ＤＩＧ□ＭＰＳ○ＭＰ４) <kazuhiro3.hayashi@toshiba.co.jp> Subject: Re: [isar-cip-core 2/2] README_version-release-policy.md: Add product description details On 01.09.23 10:19, Sai.Sathujoda@toshiba-tsip.com wrote: > 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. respective > > 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) We are not building products in the CIP project. > > ## 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 | This is like a mini changelog, in addition to the full changelog (git history) and the release summaries. What is the purpose if this table, who is expected to read that? Jan -- Siemens AG, Technology Linux Expert Center
On 26.10.23 10:56, Sai.Sathujoda@toshiba-tsip.com wrote: > Hi Jan, > > We are thinking that this description table will help in Configuration management as well as in future where one can refer this to know the features for specific release. This will help to create images of their choice. > > E.g. version v1.1 meta-data is used to create evaluation images with some specific features which might have been deprecated in future point of time. Later when someone in future wants to generate an image with those specific features, then the information in this table will help. > > Please provide your opinion, Jan. All fine, but please don't duplicate existing efforts (git history + announcement emails, existing descriptions), augment them. If we want something similar to [1], let's propose / discuss that. But recording the obvious information that buster-bookworm and 4.4-6.1 are supported (kas-container menu...) in another document is not improving the situation a lot, rather creates the risk to leave that document out-of-sync behind after a while. In fact, it even fells short on describing the actually supported combinations (KERNEL_4_4 depends on !ARCH_ARM64 && !ARCH_RISCV64). Jan [1] https://github.com/ilbers/isar/blob/master/RECIPE-API-CHANGELOG.md > > Thanks and Regards, > Sai Ashrith. > > -----Original Message----- > From: Jan Kiszka <jan.kiszka@siemens.com> > Sent: Friday, September 1, 2023 4:10 PM > To: ashrith sai(ＴＳＩＰ) <Sai.Sathujoda@toshiba-tsip.com>; cip-dev@lists.cip-project.org > Cc: dinesh kumar(ＴＳＩＰ TMIEC ODG Porting) <dinesh.kumar@toshiba-tsip.com>; hayashi kazuhiro(林 和宏 ＤＭＥ ○ＤＩＧ□ＭＰＳ○ＭＰ４) <kazuhiro3.hayashi@toshiba.co.jp> > Subject: Re: [isar-cip-core 2/2] README_version-release-policy.md: Add product description details > > On 01.09.23 10:19, Sai.Sathujoda@toshiba-tsip.com wrote: >> 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. > > respective > >> >> 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) > > We are not building products in the CIP project. > >> >> ## 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 | > > This is like a mini changelog, in addition to the full changelog (git > history) and the release summaries. What is the purpose if this table, who is expected to read that? > > Jan > > -- > Siemens AG, Technology > Linux Expert Center
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 |