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

release-schema: update tag and publisher description for compiled releases #1712

Open
wants to merge 3 commits into
base: 1.2-dev
Choose a base branch
from

Conversation

odscjen
Copy link
Contributor

@odscjen odscjen commented Nov 5, 2024

closes #330

@@ -27,13 +27,13 @@
},
"publisher": {
"title": "Publisher",
"description": "The original publisher of this release.",
"description": "The original publisher of the release. For a compiled release this may differ from the publisher(s) of the individual releases about the contracting process.",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use non-normative synonym. Add "or planning process".

Suggested change
"description": "The original publisher of the release. For a compiled release this may differ from the publisher(s) of the individual releases about the contracting process.",
"description": "The original publisher of the release. The publisher of a compiled release for a contracting or planning process might differ from the publishers of its releases.",

Copy link
Contributor Author

@odscjen odscjen Nov 7, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But the schema is supposed to be normative?

Agree with the rest of the re-wording and have applied

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the first sentence sets the normative semantics, and the second sentence provides some additional guidance to aid interpretation. I might be wrong, though!

schema/release-schema.json Outdated Show resolved Hide resolved
docs/schema/merging.md Outdated Show resolved Hide resolved
docs/schema/merging.md Outdated Show resolved Hide resolved
docs/schema/merging.md Outdated Show resolved Hide resolved
docs/schema/merging.md Outdated Show resolved Hide resolved
docs/schema/merging.md Outdated Show resolved Hide resolved
@odscjen odscjen requested a review from jpmckinney November 8, 2024 09:27
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.

Update release schema to be coherent with merging specification
2 participants