Lines Matching full:version

5 ## Version numbering
7 MCUboot uses [semantic versioning][semver], where version numbers
11 1. MAJOR version when there are incompatible API changes.
12 2. MINOR version when new functionalities were added in a
14 3. PATCH version when there are backward-compatible bug fixes.
18 In the documentation, we mark an MCUBoot development version using the
47 It requires its version to be updated by editing
48 `scripts/imgtool/__init__.py` and modifying the exported version:
53 This version should match the current release number of MCUboot. The
65 new release version, including updates to the pseudo keys
70 There is a version file used by Zephyr builds to indicate the version
72 `boot/zephyr/VERSION`. For alignment with Zephyr versions, development
79 To make a release, make sure your local repo is on the tip version by
83 Create a commit on top of the branch that modifies the version number
85 change, with a commit text similar to "Bump to version a.b.c".
86 Having the version bump helps to make the releases
122 Mark the MCUboot version as a development version.
124 The version number used should be specified for the next expected release.
125 It should be larger than the last release version by incrementing the MAJOR or
126 the MINOR number. It is not necessary to define the next version precisely as
127 the next release version might still be different as it might be needed to do: