feat: establish release lifecycle for v3.1.0#67
Merged
Conversation
Addresses issue #66. Three consumers (glossarist-ruby, glossarist-js, concept-browser) vendor concept-model artifacts and were diverging because there was no tag past v3.0.0 (14 commits behind HEAD). Added: - RELEASE_NOTES.md — v3.1.0 release with consumer-facing impact table - CHANGELOG.md — rolling log (Keep a Changelog format) - RELEASE_PROCESS.md — semver policy and release checklist - .github/workflows/release-reminder.yml — posts a reminder comment on PRs that touch ontologies/ or schemas/ (does NOT auto-tag; tagging remains a maintainer decision) - README.adoc — Versioning and releases section with semver table Semver assessment: v3.1.0 (MINOR). All 14 commits since v3.0.0 are additive — new classes, properties, shapes, examples. No existing URI was removed or renamed. The xl: → skosxl: prefix spelling change preserves the same IRI binding.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes #66.
Summary
Establishes the tag lifecycle policy requested in issue #66. Three consumers (glossarist-ruby, glossarist-js, concept-browser) vendor concept-model artifacts and were diverging because there was no tag past v3.0.0 (14 commits behind HEAD).
Added
RELEASE_NOTES.mdCHANGELOG.mdRELEASE_PROCESS.md.github/workflows/release-reminder.ymlontologies/orschemas/README.adocSemver: v3.1.0 (MINOR)
All 14 commits since v3.0.0 are additive. No existing URI was removed or renamed. The
xl:→skosxl:prefix change preserves the same IRI binding (http://www.w3.org/2008/05/skos-xl#).What this does NOT do
After merge
Cut the tag:
The tag push triggers
release.ymlto create the GitHub Release.