Skip to content
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

Describe versioning principles #41

Merged
merged 1 commit into from
Jan 9, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions mkdocs.yml
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,7 @@ plugins:
nav:
# - Home: home.md
- Index: index.md
- Principles: principles.md
- About: about.md
site_url: https://nfdi4cat.github.io/pid4cat-model
repo_url: https://github.com/nfdi4cat/pid4cat-model
Expand Down
12 changes: 12 additions & 0 deletions src/docs/files/principles.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
# Versioning of PID4Cat-model

The versioning of the PID4Cat-model is following the **SchemaVer** scheme proposed in a [snowplow blog post](https://snowplow.io/blog/introducing-schemaver-for-semantic-versioning-of-schemas). This also matches with the [HCA schema versioning](https://github.com/HumanCellAtlas/metadata-schema/blob/master/docs/evolution.md#schema-versioning) and is also adapted by [openlinaeage](https://github.com/OpenLineage/OpenLineage/blob/main/spec/Versioning.md).

**SchemaVer**: Given a version number MODEL.REVISION.ADDITION, increment the

- MODEL when you make a breaking schema change which will prevent interaction with any historical data
- REVISION when you make a schema change which may prevent interaction with some historical data
- ADDITION when you make a schema change that is compatible with all historical data

The versions are tagged in git (for example "v1.2.3").
Based on the tags we also create GitHub releases to provide easy access to all versions and to document the changes between versions.
Loading