Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions doc/source/release_process.rst
Original file line number Diff line number Diff line change
Expand Up @@ -162,6 +162,13 @@ could build. ``build (virt32)`` and ``build (virt64)`` are required status
checks on ``main`` for the same reason: merging on red stays possible for a
maintainer, but never by accident.

Check ``SO3_KERNEL_VERSION_FALLBACK`` too: it must already read the version
being tagged, since the tagged tree is what a gitless build banners. It
appears twice in this page on purpose — bump it **in the release commit set**
so the tag is right, and again when propagating to ``main`` so the next
release does not start a version behind (``main`` sat at ``6.2.4`` while
``release/v6.2`` was at ``6.2.5``).

Rules of thumb
**************

Expand Down
2 changes: 1 addition & 1 deletion so3/so3/include/version.h
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@
* (see scripts/so3version.sh and include/generated/autoversion.h). Keep this in
* sync with the current release tag as a safety net.
*/
#define SO3_KERNEL_VERSION_FALLBACK "6.2.4"
#define SO3_KERNEL_VERSION_FALLBACK "6.3.0"

/* Release version resolved at build time (git tag -> base version). */
#include <generated/autoversion.h>
Expand Down
Loading