-
Notifications
You must be signed in to change notification settings - Fork 88
Jakarta Standard Tag Library 3.1.0 plan review #824
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
base: master
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for jakartaee-specifications ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for jakartaee-specifications ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for jakartaee-specifications ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
# Details | ||
* [Jakarta Standard Tag Library 3.1 Release Record](https://projects.eclipse.org/projects/ee4j.jstl/releases/3.1.0) | ||
<!-- The following can be uncommented and version information updated as they become available. | ||
* [Jakarta Standard Tag Library 3.0 Specification Document](./jakarta-tags-spec-3.0.pdf) (PDF) |
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.
should be 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.
This comment applies to all of the following sections.
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.
@Emily-Jiang this is currently commented out and won't be displayed anyplace, I followed a similar structure to what was done for Servlet 6.2: https://github.com/jakartaee/specifications/pull/807/files I can make these changes but they won't point to any existing artifacts. Do you still want me to update?
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.
@pnicolucci okay. I think this PRs are not consistent as some PRs have updated the versions. Anyway, it is not a big deal as you said they are commented out.
|
||
# Details | ||
* [Jakarta Standard Tag Library 3.1 Release Record](https://projects.eclipse.org/projects/ee4j.jstl/releases/3.1.0) | ||
<!-- The following can be uncommented and version information updated as they become available. |
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.
@Emily-Jiang I have a comment saying to uncomment update the version information as it become available. Is this ok given the comment?
Plan Review PR template
When creating a specification project plan review, create PRs with the content defined as follows.
Include the following in the PR: