From dfc7c5f9a4aa81a5ded6a7755f5508bd14e0d4bd Mon Sep 17 00:00:00 2001 From: Andrzej Puzdrowski Date: Fri, 30 Oct 2020 12:17:59 +0100 Subject: [PATCH] doc/release: Describe development version designation After each release version will be changed to MAJOR.MINOR.PATCH-dev. Signed-off-by: Andrzej Puzdrowski --- docs/release.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/docs/release.md b/docs/release.md index 34bd5c3d..3115b6d0 100644 --- a/docs/release.md +++ b/docs/release.md @@ -15,6 +15,9 @@ incremeting the numbers: We add pre-release tags of the format MAJOR.MINOR.PATCH-rc1. +We mark in documentation an MCUBoot development version using +the format MAJOR.MINOR.PATCH-dev. + ## Release Notes Before making a release, be sure to update the `docs/release-notes.md` @@ -81,4 +84,17 @@ git push origin HEAD:refs/heads/master git push origin va.b.c-rcn ``` +## Post release actions + +Mark the MCUBoot version as a development version. The version number used +should be specified for the next expected release. +It should be larger than the last release version by incrementing the MAJOR or +the MINOR number. It is not necessary to define the next version precisely as +the next release version might still be different as it might be needed to do: + +- a patch release +- a MINOR release while a MAJOR release was expected +- a MAJOR release while a MINOR release was expected + + [semver]: http://semver.org/