All of lore.kernel.org
 help / color / mirror / Atom feed
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 1/2] README_version-release-policy.md: Rectify "y" incremental details in metadata version
Date: Fri,  1 Sep 2023 13:49:42 +0530	[thread overview]
Message-ID: <20230901081943.1816811-1-Sai.Sathujoda@toshiba-tsip.com> (raw)

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**.
-- 
2.30.2




             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 Sai.Sathujoda [this message]
2023-09-01  8:19 ` [isar-cip-core 2/2] README_version-release-policy.md: Add product description details Sai.Sathujoda
2023-09-01 10:39   ` 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-1-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.