doc/release: Describe development version designation

After each release version will be changed to
MAJOR.MINOR.PATCH-dev.

Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no>
This commit is contained in:
Andrzej Puzdrowski 2020-10-30 12:17:59 +01:00
parent b94c985a26
commit dfc7c5f9a4
1 changed files with 16 additions and 0 deletions

View File

@ -15,6 +15,9 @@ incremeting the numbers:
We add pre-release tags of the format MAJOR.MINOR.PATCH-rc1. 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 ## Release Notes
Before making a release, be sure to update the `docs/release-notes.md` 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 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/ [semver]: http://semver.org/