|[jakarta.ee-spec] Jakarta EE Spec Committee Approved Meeting Minutes - August 25th, 2021|
Attendees (present in bold):
Kenji Kazumura - Fujitsu
Dan Bandera - IBM - Kevin Sutter, Tom Watson
Ed Bratt - Oracle - Dmitry Kornilov
Andrew Pielage - Payara
Scott Stark - Red Hat - Mark Little, Scott Marlow
David Blevins - Tomitribe - Jean-Louis Monteiro, Cesar Hernandez
Ivar Grimstad - PMC Representative
Marcelo Ancelmo - Participant Member - Martijn Verburg
Werner Keil - Committer Member
Jun Qian - Primeton - Enterprise Member
Eclipse Foundation: Tanja Obradovic, Paul Buck (chair)
Past business / action items:
Approval is requested for the meeting minutes from the July 28th meeting as drafted - Approved.
Jakarta EE 10 Plan Review - Candidate specifications
Since our previous call on July 28th, the following resolution was approved by ballot on the Spec Discussions mailing list “RESOLUTION: The Jakarta EE Specification Committee resolves that no new optional features may be added in Jakarta EE 10 and beyond in component, Platform, or Profile specifications.”. Proposed next steps for discussion:
This resolution needs to be communicated to the specification projects
Send result to spec leads mailing list ASAP [Scott Stark]
Platform and Profiles (Web & Core) release plans note this requirement and handled within discussions on the Platform calls [Kevin, Scott Stark, Ivar]
Document it in the release checklist [Template was updated, see https://github.com/jakartaee/specifications/pull/414, review w/ Kevin in next call]
Update JESP & Operations Guide [Scott Stark]
Release Reviews for specifications that are not in compliance will not proceed to ballot, spec projects will be requested to be in compliance prior to ballot.
The summary of the ballot is below:
* - vote arrived after the ballot was closed so was not included in the tally.
How best to handle dormant specs such as the Stable APIs Project. No activity does not always imply that the project is dead and can be terminated, it may need an errata in the future for a change needed to support a new Java SE release.
Could the inactive projects access infrastructure from a pool instead of static allocation of build infrastructure?
What if a CVE comes in that affects a specification, requiring a rev?
Ivar to let the Infra team to let them know that the Stable APIs Project has an on-going need for its build infrastructure.
The Jakarta Connector Spec document is 100M in size and is too large to be properly served up as a web page (HTML). Idea: rerender without the resource (images). Can this be done without re-release the artifact? Could be done as a service release.
Netlify has a 30s page serving/service limit which can cause spec doc pages to be truncated
Do not build html file as a single inline document
Go back and look at if such high-res images are required - embedded images
Move PDF and html files to the download server
Go back to Infra team and request a larger limit from “Netlify”
Review the AsciiDoc settings and do not include images by default
Move the Jakarta Connector html file to the download server and update the link on the spec page [Ed]
Find a longer term solution including requesting that “Netlify” raise their limit [Paul]
Nominations and ballots for the elected seats on the Specification Committee are expected to get underway the week of September 6th.
Chair on a go forward basis will be assessing good standing position of committee members and following up on exceptions
Subsequent to 08/25 call: The Jakarta EE Steering Committee is considering an update to the working group charter to drop the good standing requirement to align with the Eclipse Foundation AISBL bylaws. As a result no action will be taken by the Specification Committee chair at this time regarding good standing.
Back to the top