Second version integer CAN BE becomes reserved for consensus change releases, now separate from bugfix-only revisions
Edit: Or anything else, I guess. This PR simply rearranges the version number.
Clean SemVer-compatible alternative to #20223
Second version integer CAN BE becomes reserved for consensus change releases, now separate from bugfix-only revisions
Edit: Or anything else, I guess. This PR simply rearranges the version number.
Clean SemVer-compatible alternative to #20223
Second version integer becomes reserved for consensus change releases, now separate from bugfix-only revisions
Not only should this reduce confusion, it can also make it even clearer when a new softfork is included in a release.
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--174a7506f384e20aa4161008e828411d-->
Reviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.
<!--9cd9c72976c961c55c7acef8f6ba82cd-->
<!--a722867cd34abeea1fadc8d60700f111-->
<!--cf906140f33d8803c4a75a2196329ecb-->
🐙 This pull request conflicts with the target branch and needs rebase.
<sub>Want to unsubscribe from rebase notifications on this pull request? Just convert this pull request to a "draft".</sub>
This is the same Concept, but without the implementation flaws in the other PR...
Milestone
22.0