Skip to content

Initial commit for future version#12

Merged
jamesrhester merged 3 commits into
mainfrom
start_of_2.1.0
May 7, 2026
Merged

Initial commit for future version#12
jamesrhester merged 3 commits into
mainfrom
start_of_2.1.0

Conversation

@jamesrhester

Copy link
Copy Markdown
Collaborator

No description provided.

@vaitkus

vaitkus commented May 6, 2026

Copy link
Copy Markdown
Collaborator

Shouldn't the next preliminary version number should be 2.0.1 instead of 2.1.0?

That is, if the next release will only contain bugfixes then there will be no need to increment the <minor> component of the version number. Alternatively, once any new features or breaking changes are introduced, the version number can be updated as needed.

Also, do we want the version number to also contain the -dev postfix to clearly indicate that the version is not yet released as described here in [1]? The document also discusses assigning each revision a separate dev increment version, i.e. dev.0, dev.1, etc., but I doubt that anyone will want to dedicate the effort to keep this number in sync (might have been too wishful thinking on my part :) ).

[1] https://github.com/COMCIFS/comcifs.github.io/blob/main/accepted/dictionary_development_practices.md#versioning-a-development-dictionary

@jamesrhester

Copy link
Copy Markdown
Collaborator Author

Adjusted version numbering as suggested.

@jamesrhester jamesrhester merged commit 6fb33f2 into main May 7, 2026
1 check passed
@jamesrhester jamesrhester deleted the start_of_2.1.0 branch May 7, 2026 07:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants