Description
Up until now, we have slowly worked our way through issues and slowly progressed as time went on, but now it seems there is consensus to get "down to business".
In the last meeting, we discussed setting the release date and freeze period for when the last change to the spec can happen. This issue finalizing that proposal, and this is only a proposal and not an order 😄
Remember we do not have a targetted scope for spec 3.0, the scope is what has reached RFC stage 3 at the time of the release. Read more about the RFC process in the contributing guide.
Therefore this release schedule suggests a specific release period and a freeze period to give people an adequate amount of time to review the final version before it's released.
Release 3.0.0 is scheduled for June 2023
The suggestion is to release spec 3.0 at the end of June next year (in the second release period), and whatever proposals has reached RFC stage 3, at that time will be included in version 3.
Freeze period from February 2023
The suggestion is from the end of February no more new changes are allowed into spec 3.0, from then on it's only about finalizing what we have. That means that any proposals that have not reached RFC stage 2 (should it be stage 1?) will not be included in spec 3.0, regardless of whether they finish between February and the end of June.
What this means is that the only change that can happen from February onwards are:
- Review and minor edits of existing changes.
- Finalizing tooling implementations in the parser and JSON-schema-spec repository to reach stage 3 (as stage 2 does not mean the implementations are finalized).
- Removal of existing features that are deemed rejected.