| [jakarta.ee-spec] Jakarta EE Spec Committee Approved Meeting Minutes - June 16th, 2021 |
Attendees (present in bold):
Kenji Kazumura - Fujitsu
Dan Bandera - IBM - Kevin Sutter, Tom Watson
Ed Bratt - Oracle - Dmitry Kornilov
Andrew Pielage - Payara - Matt Gill
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, Wayne Beaton, Paul Buck (chair)
Past business / action items:
Approval is requested for the meeting minutes from the June 2nd meeting as drafted - Approved.
Agenda:
Ongoing tracking spreadsheet of individual specs progress through the JESP
Jakarta EE 10 Plan Review - Candidate specifications
Noting the Compatible Implementation(s) used in Release Review and the Ratification step of specifications (see June 2nd minutes for additional background)
Ivar & Kevin to present proposal, to be discussed and voted on (if required)
Proposal & consensus - leave it as is for now, revisit if needed at a future release.
Specification Committee’s input to the Q3 Jakarta EE 2021 Progress by Quarter tracking spreadsheet (also see Jakarta EE 2021 Program Plan - Quarterly Progress) [Tanja]
See the spreadsheet and presentation linked above for updates
Proposal from Dan, Kevin and Scott S. for how to handle optional features in Jakarta EE specifications including Platform and Web Profile. The proposal is here (see June 2nd minutes for additional background)
ACTION: Dan and Paul to author a resolution for the policy, once authored, post the draft to the private list for final input by committee members and then it will go to ballot on the discussion list.
DRAFT RESOLUTION (added during the call): Is to eliminate marking any Jakarta EE Specification feature as optional in some future release of each Jakarta EE Working Group Specification, including and possibly starting with the Jakarta EE Platform Specification Release 10. All remaining features would be required.
Clarifying text to the proceeding resolution: The process would be to mark all optional features in the current release as “Deprecated” in a new Minor release (Release 9.2), and in a subsequent Major release (not necessarily the very next Major release) eliminate the Deprecated feature completely from the Jakarta EE Platform Specification. Eliminating these Deprecated features is not retroactive to earlier released specifications, which will continue to exist. As implied, “Deprecated” will be defined as a way of marking a feature as on the path to complete elimination from some future release, and it indicates to the public “this feature is going away”. This two-step process provides a formal communication mechanism within the specification itself for the Working Group to signal to the community that a feature will definitely be removed from a future release. The intent is to mark current features marked as “Optional” as “Deprecated”, but in the future even “Required” features could be marked as “Deprecated” should the Working Group decide to prune little used features from the platform. This two-step process will take longer but will also give consumers of the platform a longer runway to plan for and deal with the elimination of the feature should they wish to consume that future platform release.
Next steps agreed to in the call:
Specification Committee members have requested time to review the resolution, and provide input on the Spec Committee mailing list over the next 7 days.
Following 1., send the proposal on optional features: draft resolution, clarifying text & the final version from the original document to Spec Project Leads mailing list to explain dissenting views or counter proposals over 7 days.
Target to ballot on the resolution in the Spec Committee call on June 30th.