Skip to content

add subsection to point to the github process file for proposal requirements #1613

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

Merged
merged 3 commits into from
Aug 3, 2025

Conversation

gregsdennis
Copy link
Member

What kind of change does this PR introduce?

clarification

Issue & Discussion References

Summary

Adds a new section to help identify requirements for proposals.

It does feel odd to me that the specification is now pointing to a document that could be (and still needs to be) updated.

Does this PR introduce a breaking change?

No.

@gregsdennis gregsdennis added this to the stable-release milestone Jul 13, 2025
@gregsdennis gregsdennis requested a review from a team July 13, 2025 04:56
@gregsdennis gregsdennis self-assigned this Jul 13, 2025
@gregsdennis gregsdennis moved this to In Progress in Stable Release Development Jul 13, 2025
@@ -437,6 +437,13 @@ compatible with successive specifications, which are published with the same
version and either the same or greater release year value. Thus, JSON Schema
provides a guarantee of compatibility for future releases within a version.

### Future Development and Support of Proposals

Continued development of this specifications and support requirments for
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
Continued development of this specifications and support requirments for
Continued development of this specification and support requirements for

Copy link
Member Author

@gregsdennis gregsdennis Jul 14, 2025

Choose a reason for hiding this comment

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

Oh, yeah, I meant for that to go the other way. Should be "these specifications" to include the validation spec.

Copy link
Member

@Relequestual Relequestual left a comment

Choose a reason for hiding this comment

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

With the already suggested change 👍🏻

@gregsdennis gregsdennis merged commit fb0a2ee into main Aug 3, 2025
6 of 7 checks passed
@gregsdennis gregsdennis deleted the gregsdennis/proposal-expectations branch August 3, 2025 20:37
@github-project-automation github-project-automation bot moved this from In Progress to Done in Stable Release Development Aug 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

Successfully merging this pull request may close these issues.

Core: Add section to define expectations for proposals
4 participants