xdp: Switch to a new versioning scheme - #2042
Merged
Merged
Conversation
Contributor
Just for clarity or being addressed explicitly here, the new scheme will not have things alike to |
Collaborator
Author
|
Correct. Testing can be done by building from main, just like GNOME OS does. |
Collaborator
Author
Collaborator
|
I agree the current scheme is just too confusing. |
AdrianVovk
approved these changes
Jun 24, 2026
swick
force-pushed
the
wip/new-versioning
branch
from
July 31, 2026 19:14
f3ed8ed to
92d8ea2
Compare
We currently have something which resembles semantic versioning, but the minor releases are stable when the number if even, and unstable when the number is odd. This also means the first number is fixed at 1 because we never break backwards compatibility. A lot of people get confused by the odd/even scheme. Distros like Fedora have been shipping unstable releases. Distros like Arch have not been testing any of the unstable releases. Systems like GNOME OS have started shipping xdp from git main in their nightly where we will notice when something went wrong immediately. Releases are work. Doing them needs to have a benefit. It does not seem like there is any benefit for us to do the unstable releases. Given that unstable releases are a waste of time and that the major version is fixed, this commit changes the project over to a scheme where... * all releases are stable releases * the version number is major.minor * minor versions get released to deal with security issues and bugs * only the latest major release is supported The next release will be version 23.0 because we would have releases 1.23.0 in the old versioning scheme.
swick
force-pushed
the
wip/new-versioning
branch
from
July 31, 2026 20:22
92d8ea2 to
be84a13
Compare
swick
enabled auto-merge
July 31, 2026 20:24
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
5 participants
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.
We currently have something which resembles semantic versioning, but the minor releases are stable when the number if even, and unstable when the number is odd.
This also means the first number is fixed at 1 because we never break backwards compatibility.
A lot of people get confused by the odd/even scheme. Distros like Fedora have been shipping unstable releases. Distros like Arch have not been testing any of the unstable releases. Systems like GNOME OS have started shipping xdp from git main in their nightly where we will notice when something went wrong immediately.
Releases are work. Doing them needs to have a benefit. It does not seem like there is any benefit for us to do the unstable releases.
Given that unstable releases are a waste of time and that the major version is fixed, this commit changes the project over to a scheme where...
The next release will be version 23.0 because we would have releases 1.23.0 in the old versioning scheme.