-
-
Notifications
You must be signed in to change notification settings - Fork 359
Home
Henry Andrews edited this page Oct 28, 2017
·
11 revisions
Contributions of various sorts are welcome and encouraged! Please see our guidelines for contributing for details.
Documents on master should use a WORK-IN-PROGRESS-*-NN placeholder name. Published drafts are tagged as they cannot be edited once published. In the event of a critically flawed drafts, a new drafts should be published with the fixes as soon as possible.
- If a new meta-schema URI is required, ensure that all documents reflect it
- Tag each commit with the name(s) of the draft(s) published from that commit
- Publish the new draft(s) through the IETF Datatracker I-D submission page
- Update the HTML versions on the website
Meta-schemas on master should be numbered for the forthcoming draft, and have a -wip (Work In Progress) suffix in their URI, e.g. http://json-schema.org/draft-07-wip/schema. Meta-schemas are branched as they are non-normative and can accept bug-fixes (and the last three published meta-schema versions have needed bug-fixes).
To publish a meta-schema:
- Make and switch to a branch with the draft number, e.g.
draft-07 - Remove
-wipfrom$idand commit the result - Create a new submodule in the web site repo, pointing to the branch
- On master, increment the draft (retaining the
-wipsuffix) and commit the result