Lines Matching refs:to
24 to describe the release. This should be a high-level description of
31 should be removed to ready the directory for the next release cycle.
38 is to freeze the code and allow testing.
41 that should be merged into the main branch are those to fix bugs found
47 It requires its version to be updated by editing
63 the RC step is finished, the release needs to be exported by modifying
65 new release version, including updates to the pseudo keys
70 There is a version file used by Zephyr builds to indicate the version
71 of MCUboot being used which needs to be updated at
73 versions should set `PATCHLEVEL` to `99` and `EXTRAVERSION` to `dev`,
85 change, with a commit text similar to "Bump to version a.b.c".
86 Having the version bump helps to make the releases
87 easier to find, as each release has a commit associated with it, and
88 not just a tag pointing to another commit.
95 The releaser will need to make sure that git is configured to use the
96 proper signing key, and that the public key is signed by enough parties to
99 At this point, the tag can be pushed to GitHub to make the actual release
117 This branch will be used to generate new incremental `PATCH` releases
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: