Skip to content

Remove partial archive of meta-schemas #459

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 1 commit into from
Nov 7, 2017

Conversation

handrews
Copy link
Contributor

We're not keeping this up-to-date and we don't use it on the web
site either, so let's get rid of it. We've already had one bit
of confusion over differences in formatting between theses and
the published ones.

We're not keeping this up-to-date and we don't use it on the web
site either, so let's get rid of it.  We've already had one bit
of confusion over differences in formatting between theses and
the published ones.
Copy link
Member

@dlax dlax left a comment

Choose a reason for hiding this comment

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

Looks reasonable since there are branches for each draft.

@awwright
Copy link
Member

Is there anything to keep up-to-date? The meta-schemas never change.

The idea is to have this be the canonical definition of meta-schemas (unless the canon one published prior to this repository was different, in which case we should fix the mistake).

I suppose we don't strictly need this, but I'd like to see something lay out what is supposed to be defined where.

@handrews
Copy link
Contributor Author

We have fixed mistakes in 4 meta-schema files across 3 draft revisions in the last month.

All of the meta-schema versions are published through the web site repo, so I don't see the point of having them here. We have gotten at least one confused person on the mailing list b/c they got out of sync.

@handrews
Copy link
Contributor Author

I'd like to see something lay out what is supposed to be defined where.

@awwright could you explain what this means exactly?

The canonical versions are git submodule'd in to the web site repo based on a branch or tag. Currently I have branches for draft-03, draft-04, and draft-06 because they had bugs, but I was planning on replacing those with tags once it seems pretty likely that we have the bugs sorted.

@handrews
Copy link
Contributor Author

handrews commented Nov 7, 2017

No reply after a week, and the comment was not an outright objection, so I'm going to merge this. Whatever it is that you meant by "lay out what is supposed to be defined where", please file it as a new issue.

@handrews handrews merged commit 9e554cc into json-schema-org:master Nov 7, 2017
@handrews handrews deleted the no-archive branch November 7, 2017 05:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants