-
Notifications
You must be signed in to change notification settings - Fork 822
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
Meta-issue for upcoming release, drafted as v3.6 in master branch #2193
Comments
There are comments from @philbarker that may still need attention.
/cc @vholland |
Commited, needs release notes:
|
Candidate Pull Requests:
Candidate moves from pending to core:
|
Two PRs adding what I think are missing
|
maybe https://github.com/schemaorg/schemaorg/issues/2170 too regarding DefinedTerm etc., it is a substantial sub-vocabulary, I'd like to see signs that it is being consumed somewhere. |
#1606 closed after discussion |
Ok, I have made a pass through the issues above (thanks, @RichardWallis). Many are merged in (I've ticked them off inline in the Github comment). Some need more time and consideration. Merged in for 3.6 release candidate review#2203 Add Service to rangeIncludes of orderedItem More work needed#2205 Add new property accessRights with domainIncludes CreativeWork (and everything else) |
For future releases, let's require every pullrequest to include text for docs/releases.html. This time around I'll do it, but it will help with keeping up momentum if that work can be distributed. |
Placeholder for 3.7: we need to look again at GeoShape properties like 'box', it seems the ordering of lat-then-long is not made clear enough (unless digging into the ancestor schemas at rNews etc). |
Created an issue for 3.7, #2239 |
Stale issue message |
Tracking issue for upcoming 3.6 release
The text was updated successfully, but these errors were encountered: