Repository navigation
Replies: 2 comments 2 replies
|
Kubebuilder releases follow the Semantic Versioning convention. The latest release, v4.13.0, does not appear to be a patch release because it includes at least one new feature:
Under SemVer, adding a new feature should result in a minor version bump rather than a patch release. I hope that clarifies your question. |
|
Wanted to add a bit of context here too:
Even if a release has many bug fixes, if it has just one new feature, it should be minor release, because that's what SemVer is meant to convey. An example that might make it clearer when this is useful is if a release had many features, but just one breaking change. It should be a major release in that situation even if most of the changes were new features, because users need to be informed that there was a breaking change that might affect them. If they upgraded without checking whether the breaking change affected them first, they could be negatively affected. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello everyone,
I am watching the semver naming convention of the last few kubebuilder releases and IMHO it looks like it doesn't deserve minor release number upgrade. The latest releases have mostly fixes and not new fearures.
Can anyone explain to me why the Y in X.Y.Z is being bumped up that often in Kubebuilder ?
Kind regards
P
All reactions