| Message ID | 20230901081943.1816811-1-Sai.Sathujoda@toshiba-tsip.com (mailing list archive) |
|---|---|
| State | Accepted |
| 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> > > isar-cip-core regular releases are not triggered by Debian point releases. Details > regarding what the regular releases consist of are also added. > > Signed-off-by: Sai <Sai.Sathujoda@toshiba-tsip.com> > --- > doc/README_version-release-policy.md | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/doc/README_version-release-policy.md b/doc/README_version-release-policy.md > index b0b8591..918e77a 100644 > --- a/doc/README_version-release-policy.md > +++ b/doc/README_version-release-policy.md > @@ -16,7 +16,7 @@ The isar-cip-core metadata follows semantic versioning system i.e **x.y.z** form > 1. **z** is incremented only when critical bugs are fixed. If **z** is zero, it will be left out. > * For example, if the latest release version is **2.2.5**, then the upcoming release version after fixing some critical bugs will be **2.2.6**. > > -2. **y** is incremented for each Debian point release or in case of isar-cip-core regular release. When **y** is incremented, **z** is reset to 0. > +2. **y** is incremented in case of isar-cip-core regular release. When **y** is incremented, **z** is reset to 0. Regular releases include modifications in recipes, addition of new features, bringing changes when updates are announced in CIP Kernel and Debian releases. > * Let us assume that the latest release version is **2.1.1**, then the upcoming regular release version will be **2.2**. > > 3. **x** is incremented when significant changes are done other than **y** and **z**. Thanks, applied. Jan
diff --git a/doc/README_version-release-policy.md b/doc/README_version-release-policy.md index b0b8591..918e77a 100644 --- a/doc/README_version-release-policy.md +++ b/doc/README_version-release-policy.md @@ -16,7 +16,7 @@ The isar-cip-core metadata follows semantic versioning system i.e **x.y.z** form 1. **z** is incremented only when critical bugs are fixed. If **z** is zero, it will be left out. * For example, if the latest release version is **2.2.5**, then the upcoming release version after fixing some critical bugs will be **2.2.6**. -2. **y** is incremented for each Debian point release or in case of isar-cip-core regular release. When **y** is incremented, **z** is reset to 0. +2. **y** is incremented in case of isar-cip-core regular release. When **y** is incremented, **z** is reset to 0. Regular releases include modifications in recipes, addition of new features, bringing changes when updates are announced in CIP Kernel and Debian releases. * Let us assume that the latest release version is **2.1.1**, then the upcoming regular release version will be **2.2**. 3. **x** is incremented when significant changes are done other than **y** and **z**.