-
Notifications
You must be signed in to change notification settings - Fork 29
Start 1.1.0 from 1.0.0 with simplified branch setup #183
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
Conversation
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
- v1.1-dev schema versions - one test script looping over all schema versions - publishing script skips dev schema versions
7df5450 to
1328218
Compare
baywet
previously approved these changes
Oct 21, 2025
Contributor
Author
|
I think I covered everything now in the added CONTRIBUTING.md |
baywet
previously approved these changes
Oct 21, 2025
mikekistler
reviewed
Oct 27, 2025
6d10b86 to
9e6d817
Compare
9e6d817 to
0ff7a7c
Compare
baywet
approved these changes
Oct 27, 2025
mikekistler
approved these changes
Oct 27, 2025
Contributor
mikekistler
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! 👍
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As discussed in today's Overlays Meeting #172, use a simplified approach where everything happens on
mainwith short-lived PR branches (preferrably in forks).On release a spec version is moved from
dev-versionstoversions, preserving its commit history. Its schema and schema test folders are renamed and lose the-devsuffix.Schema versions are in perpetual maintenance and start directly in the
schemasfolder.Commit c4a5c3e adds file
dev-versions/1.1.0.mdwhich is an adjusted copy ofversions/1.0.0.md:Commit 1328218 adds folder
schemas/v1.1-devwhich is an adjusted copy ofschemas/v1.0:and similar adjustments in file
README.md.It also adds folder
tests/v1.1-devwhich is an adjusted copy oftests/v1.0, the only difference being the value of theoverlayfield in thepassandfailtest cases, for exampleIt also adjusts related scripts and workflows:
.github/workflows/schema-publish.yamlhas an adjusted branch name and an updated list of reviewersscripts/schema-publish.shskips folders for schemas under development with suffix-devtests/schema.test.mjsmoved to the parent folder and now loops over all schema version foldersCommit d29c651 updates section "Branching Strategy" in
CONTRIBUTING.mdand describes the new setup.