so3: set the fallback release version to 6.3.0 - #317
Merged
Conversation
Bump it before cutting release/v6.3, as version.h asks: a build from a tree without git metadata (tarball, bitbake workdir copy) banners this constant. main was still reading 6.2.4 — the 6.2.5 resync lives on release/v6.2 only, since the after-tag propagation carries the CHANGELOG, the README table and the recipe pins but not this constant. Worth remembering when cutting the next release from main.
The propagate checklist already lists SO3_KERNEL_VERSION_FALLBACK, but the constant matters twice: in the release commit set, so the tagged tree banners the right version, and again on 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 because only the second half was obvious.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepares the
v6.3.0cut:SO3_KERNEL_VERSION_FALLBACKis what a build from a tree without git metadata (tarball, bitbake workdir copy) banners, so it has to be right before the tag —v6.2.4shipped it a release behind, whichv6.2.5then had to fix.Note:
mainwas still reading 6.2.4. The 6.2.5 resync lives onrelease/v6.2only, because the after-tag propagation tomaincarries the CHANGELOG, the README table and the recipe pins — not this constant. Worth adding to the checklist.release/v6.3is branched frommainonce this lands.