Create tests for new (upcoming?) meta-schema

[awwright]

The latest I-D makes a handful of additions and changes. Copy, modify, and add tests as appropriate -- when the meta-schema is eventually published.

[Relequestual]

Is there a changelog?

[handrews]

@awwright are you actively working on this? I was going to add cases for the spec changes that I've written, but don't want to duplicate work. Let me know if there is anything you'd like me to pick up.

[Relequestual]

If either of you are working on this, should probably be in a branch in this repo, right? =]

[handrews]

If either of you are working on this, should probably be in a branch in this repo, right? =]

Probably :-) I'm a little unclear on the branching strategy for this repo, and also whether it's the right time to populate a draft 6 directory or not.

[Relequestual]

You'd have to ask @Julian on that one =]

[Julian]

6, have I already missed that much :)?

I'm not 100% happy with two branches here (I started with two, but then once or twice someone wanted an actual "cut" release with a version number, which kind of makes having two branches pointless) but I haven't changed it because I recommend people make use of the test suite via git subtrees, and I assume some people have subtree'd into develop (which wouldn't be a problem other than the next time they subtree pull'ed they'd need to come check that hey yeah develop went away just use master).

TL;DR: yeah, feel free to work off of develop (add some tests in a new branch off of develop, send a PR targeting develop, have someone review it [not necessarily me, whoever feels comfortable doing so] etc.), and definitely starting work sounds good to me, especially if I've managed to miss an entire draft release :)

[seagreen]

@Julian and @Relequestual I opened an issue on the website's repo suggesting we make a page listing every single specification draft along with links to their respective changelogs. Hopefully if we do decide to make such a page it will get a little harder to fall behind.

[handrews]

@Julian we're trying to wrap up what we have now as Draft 6, in part to address errors that crept in to Draft 5. And also to get an updated meta-schema out there, which is important to some of us.

I laid out a scope for v6 in json-schema-org/json-schema-spec#137 (comment)

[Julian]

@handrews sounds great will have a look there

[handrews]

@Julian I should probably pull that comment out an make a v6 release tracking issue...

[Relequestual]

If either of you are working on this, should probably be in a branch in this repo, right? =]

[epoberezkin]

Could we instead of duplicating all the tests in draft-06 only add the additional tests (given that draft 6 is backwards compatible)? And tell everybody that draft04 tests should pass too (maybe mark those we want to drop, like "1.0 not an integer")? The advantage is that it will be easy to see what has been added.