Fix of Calendar Version Pattern #485
Merged
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.
Pull Request Description: Fix of Calendar Version Pattern
This pull request addresses the versioning format used throughout the project, aligning it with more standard semantic versioning practices.
Changes Made:
Version Format Update:
dsg_lib/__init__.py
,makefile
, andpyproject.toml
to2025.04.05-001
instead of the previous25.04.05-001
. This change makes the versioning more consistent and semantically meaningful.tool.bumpcalver
section of thepyproject.toml
to utilize a four-digit year (%Y
) instead of a two-digit year (%y
), which further enhances clarity in versioning.Coverage and Report Files:
coverage.xml
andreport.xml
files to reflect the current state of the build, ensuring that these files are in sync with the new versioning.Motivation:
The primary motivation behind this change is to adopt a versioning scheme that complies with common conventions, making it easier for developers and users to understand the progression and compatibility of the library. The new version format also helps in better tracking of releases and their corresponding features or fixes.
Impact:
By implementing this versioning fix, we enhance the maintainability and clarity of the project. This change is expected to improve collaboration among developers and provide users with a clear understanding of the library's evolution over time.