| [jakarta.ee-spec.committee] Review for approval: Spec Committee Meeting Minutes July 24th, 2019 |
Attendees (present in bold):
Kenji Kazumura - Fujitsu, Michael DeNicola
Dan Bandera - IBM, Kevin Sutter, Alasdair Nottingham, BJ Hargrave
Bill Shannon - Oracle, Ed Bratt, Dmitry Kornilov, Will Lyons
Steve Millidge - Payara, Arjan Tijms
Scott Stark - Red Hat, Mark Little, Antoine Sabot-Durand
David Blevins - Tomitribe, Richard Monson-Haefel, Jean-Louis Monterio
Ivar Grimstad - PMC Representative
Alex Theedom - Participant Member
Werner Keil - Committer Member
Eclipse Foundation: Wayne Beaton, Tanja Obradovic, Paul Buck, Mike Milinkovich
Past business / action items
Minutes from July 17th meeting - Approved
Wiki: Outstanding updates required to the How to Prepare API Projects for the Jakarta EE 8 Release.
Question/Action: Is an Eclipse Development Process release review required for each of the specification projects at the same time we are doing the Spec Process release review? @Wayne to write up a proposal that will be discussed on the mailing list.
Balloting:
Jakarta EE 8 Staging Plan - Staggered/staged specification voting plan timeline and implications for September 10th Jakarta EE 8 target release date
Degree of serialization required?
How to run ballot’s on spec releases?
How to approve spec release PRs?
Do we have everything listed we need to verify PRs?
It is possible that PRs cannot have their upstream dependencies satisfied, so we need to be checking that API JAR releases are using the correct dependency versions.
Discussion/Questions on the above:
Will review be done during ballot period or ahead? Needs to be done ahead.
Do all spec committee members to review all PR? Yes. This must be done ahead of the spec committee call.
Start ballot when each spec project is ready in batches at scheduled calls or in a single lot? When ready.
Which PR does the committee review on Friday? Deferred to next week’s Wednesday call.
What checklist or criteria does the committee use to approve a PR? Not discussed.
When is a candidate compatible implementation required? We need one/first to bootstrap the voting and begin the ballot. As per the TCK process an issue needs to be filed against the TCK project to demonstrate it meets the certification requirement. Action: update the API Prepare wiki page and update the PR template as required.
The topics that follow were not discussed in the July 24th call.
Specification Project topics:
CDI spec project provisioned and data moved over
Jakarta XML specifications that are not included in Jakarta EE 8. Are these ones required for the release review?
Jakarta XML Web Services
Jakarta Web Services
Jakarta SOAP with Attachments
Specifications website / pages update and outstanding work items [Wayne]
Process: Publish the fully approved JESP 1.2 (pull request)
JakartaOne Livestream (https://jakartaone.org/) update [Tanja]