-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ease the process of code versioning #3035
Comments
So, if I iterate on my branch, the version number will not change. |
We should also keep this issue in mind. |
@castelletto1 What do we want to do regarding this? |
if #3043 is merged, it will be easy to add versions by following the semantic conventions of the merged commit messsages. |
What is the requested feature?
Automate the code versioning process to have effective versioning of the code and maybe releases.
Is your request related to a specific problem?
I would like an easy, human readable, comparable way to discriminate versions of the public API (i.e. represented as xsd files #2971). Not sure a commit hash is the right way.
Describe the solution you'd like
I was thinking to something close to semver.
But, doing it manually is painful and time consuming.
So what about using a github-action like this one: https://github.com/ietf-tools/semver-action.
It will flow seamlessly for those using commit prefixes.
For the others, we could simply avoid the
patch
part and adopt a simple algorithm like this one:This action will make the next version available as a variable in the pipeline.
It should then be easy to patch the CMakeLists, a header file, xsd schemas, or whatever...
What to you think ?
Describe alternatives you've considered
n.a.
Additional context
n.a.
Related: #3043
The text was updated successfully, but these errors were encountered: