Navigation Menu

Skip to content
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.7 in master branch #2239

Closed
danbri opened this issue May 1, 2019 · 13 comments
Closed

Meta-issue for upcoming release, drafted as v3.7 in master branch #2239

danbri opened this issue May 1, 2019 · 13 comments
Assignees
Labels
no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!).

Comments

@danbri
Copy link
Contributor

danbri commented May 1, 2019

Tracking issue for upcoming release

  • Target date: 2019-06-01 (officially Saturday June 1st 2019; freeze on Friday May 31st, publish Monday June 3rd)
  • Circulate for review on or before: 2019-05-20 (Monday May 20th 2019)
@RichardWallis
Copy link
Contributor

RichardWallis commented May 2, 2019

Candidate Pull Requests:

@philbarker
Copy link
Contributor

Maybe add

@twamarc
Copy link
Contributor

twamarc commented May 16, 2019

Hi @RichardWallis and @danbri: Please advise if we add the #2214 on this release? just to see if I need to prioritise the task. (I would rather suggest to plan it for the next release)

@RichardWallis
Copy link
Contributor

@twamarc You can create a PR for the fix whenever, then we can look to feeding into the next appropriate release.

@danbri
Copy link
Contributor Author

danbri commented May 17, 2019

also tweak for estimatedSalary values, #2251

@philbarker
Copy link
Contributor

How about #2247 adding properties for when a job in a jobPosting starts?

@RichardWallis
Copy link
Contributor

#2247 and #2254 (tweaks for estimatedSalary ) added to candidate list

@danbri
Copy link
Contributor Author

danbri commented May 22, 2019

"accessRights" (#2205) is a very thorny topic, I don't see any sign of sufficient consensus or data-consuming apps. #2241 deserves continuing discussion too...

I've circulated the following as a v3.7 release proposal:

#2207 Expanded rangeIncludes of occupationalCategory & jobTitle
#2170 Add named inverse for hasMenuItem
#2074 Clarifying relative sizes of region and locality in PostalAddress
#2168 Update issue-1698-examples.txt (fix broken JSON-LD)
#2136 Fixing some typos and missing commas in Schedule Example 4 json-ld
#2132 Adding some hierarchy to the documentation page
#2041 Update accessModeSufficient to expect ItemList and correct first example
#2028 isBasedOn definition and examples
#1991 releases.html: changed 3 links from 'webschemas.org' to 'schema.org'
#2254 Extend range of estimatedSalary to include MonetaryAmount and Number
#2247 adding properties to JobPosting to indicate when job starts

https://lists.w3.org/Archives/Public/public-schemaorg/2019May/0007.html

@vholland
Copy link
Contributor

I commented on #2207. I think it is a mistake to remove occupationalCategory from JobPosting as that breaks existing markup on the web.

@danbri
Copy link
Contributor Author

danbri commented May 22, 2019 via email

@danbri
Copy link
Contributor Author

danbri commented Jun 13, 2019

I've created #2272 for our next release, due out on Monday July 1st. This means we ought to be wrapping up a release candidate ASAP. There were a number of items from this issue which didn't get finalized in June's release, so let's start there...

@philbarker
Copy link
Contributor

I've been meaning to ask why #2247 didn't make the june release? Hope it can be in for July

@github-actions
Copy link

Stale issue message

@github-actions github-actions bot added the no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!). label Jul 16, 2020
@danbri danbri closed this as completed Jul 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!).
Projects
None yet
Development

No branches or pull requests

5 participants