State that we have a release process and what phase we are in #421
Conversation
…lack server. Resolves json-schema-org#98 Resolves json-schema-org#99 Resolves json-schema-org#100
|
✔️ Deploy Preview for condescending-hopper-c3ed30 ready! 🔨 Explore the source changes: 5723652 🔍 Inspect the deploy log: https://app.netlify.com/sites/condescending-hopper-c3ed30/deploys/618510ed2a2c2d0007e0d94e 😎 Browse the preview: https://deploy-preview-421--condescending-hopper-c3ed30.netlify.app/ |
| We have a twice yearly release cycle for the specification. | ||
|
|
||
| We are currently in the "patch release" cycle which is tracked by [Milestone 9](https://github.com/json-schema-org/json-schema-spec/milestone/9). | ||
|
|
||
| One release includes new features ("feature release"), while the other release includes non-controversial clarifications and corrections that do not change compliance requirements ("patch release"). These should be spaced roughly 6 months apart. |
There was a problem hiding this comment.
I think saying we release twice a year could be misleading. I think we should say that we aim for a major release once a year. Then we can say that we also try to do a patch update mid-cycle if needed. I wouldn't call the patch a "release" because there's nothing new being introduced. Implementations don't need to update their code and schema authors don't need to update their schemas.
|
Closing this as it will likely need to be redone anyway in light of the SDLC proposal. |
This is a draft PR as it should be merged after my branch
home/community-links.Resolves json-schema-org/community#101
Only review commit
5723652b8f0806f280928be33792be7acbd4e3d0