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
Jakarta RESTful Web Services 3.1 #430
Conversation
Signed-off-by: Santiago Pericasgeertsen <santiago.pericasgeertsen@oracle.com>
✔️ Deploy Preview for jakartaee-specifications ready! 🔨 Explore the source changes: 70f9bae 🔍 Inspect the deploy log: https://app.netlify.com/sites/jakartaee-specifications/deploys/621e30d61a9b3e0007c3c1f5 😎 Browse the preview: https://deploy-preview-430--jakartaee-specifications.netlify.app/specifications/restful-ws/3.1/jakarta-restful-ws-spec-3.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See my comment about the plan review ballot results
Signed-off-by: Santiago Pericasgeertsen <santiago.pericasgeertsen@oracle.com>
Signed-off-by: Santiago Pericasgeertsen <santiago.pericasgeertsen@oracle.com>
Spec Review Checklist
|
@ivargrimstad Should I be going over the latest checklist you pasted or is that for you? |
Did I scare you with this long list? :) |
Add minutes for November 9 platform call
@ivargrimstad could you have a look and try to determine why this deploy preview has failed? (Servlet PR deploy preview has also failed.) |
It looks like the API for project metadata was down when the last commit was made. Should be alright again when a change is made so the build is initiated again. |
@spericas Any predictions when you may go forward with this PR? |
@ivargrimstad We have just a couple of PR's related to TCK's almost ready. I'd say no later than next week. |
…ease. Signed-off-by: Santiago Pericasgeertsen <santiago.pericasgeertsen@oracle.com>
@ivargrimstad Pushed update of spec and apidocs for 3.1. Also latest jars are in staging and so is Jersey's milestone release that passes the TCKs. |
Signed-off-by: Santiago Pericasgeertsen <santiago.pericasgeertsen@oracle.com>
The copyright footer in the Javadoc should be "Copyright © 2018, 2022 Eclipse Foundation." The same goes for the spec doc, which is currently "...2018, 2021..." |
Signed-off-by: Santiago Pericasgeertsen <santiago.pericasgeertsen@oracle.com>
Signed-off-by: Santiago Pericasgeertsen <santiago.pericasgeertsen@oracle.com>
Done. |
@ivargrimstad Should I go ahead and merge it now? |
@spericas No, Ivar will merge this after the spec committee completes the final ballot. |
@spericas The items of the checklist in the PR, the one on the top, not the longer Review checklist I am using, need to be done. Currently, what's missing are the process steps for a release review, the TCK and a certification request. |
|
Signed-off-by: Santiago Pericasgeertsen santiago.pericasgeertsen@oracle.com
Specification PR template
When creating a specification project release review, create PRs with the content defined as follows.
Include the following in the PR:
https://github.com/jakartaee/specification-committee/blob/master/spec_page_template.md
Instructions MAY be by reference.
https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/ws/rs/jakarta.ws.rs-api/3.1.0/
https://download.eclipse.org/ee4j/jakartaee-tck/jakartaee10/staged/eftl/jakarta-restful-ws-tck-3.1.0.zip
Compatibility Certification Request for Eclipse Jersey 3.1.0-M3 rest#1104
If desired, an optional second PR can be created to contain just the JavaDoc in the
apidocs
directory.Note: If any item does not apply, check it and mark N/A below it.