Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jakarta.ee-spec.committee] Review for approval: Spec Committee Meeting Minutes January 22nd, 2020

The minutes for the January 22nd Specification Committee call are below and are also available here. Please review and be ready for approval during our next call which is on February 4th.

Spec Committee Agenda January 22, 2020

Attendees (present in bold):

Kenji Kazumura - Fujitsu - Michael DeNicola, Jacques Durand

Dan Bandera - IBM - Kevin Sutter, Alasdair Nottingham

Bill Shannon - Oracle - Ed Bratt, Dmitry Kornilov

Mark Wareham - Payara - Matt Gill

Scott Stark - Red Hat - Mark Little, Antoine Sabot-Durand

David Blevins - Tomitribe - Jean-Louis Monterio, Cesar Hernandez

Ivar Grimstad - PMC Representative

Alex Theedom - Participant Member

Werner Keil - Committer Member


Eclipse Foundation: Wayne Beaton, Tanja Obradovic, Paul Buck


Past business / action items:

  • The minutes from the January 8th meeting are approved. 

Reminder: Can be approved by lazy consensus.


Agenda

  • Note: Release of Java EE full text Spec Documents from the JCP from the Foundation to spec projects is now fully approved

https://docs.google.com/spreadsheets/d/18SraPxRBCOyaS6w-UV6TR-UA1bWy1--sV0ky6msAjWY/edit#gid=2062070702

Thanks to all that contributed to this outcome.

  • Updates to the jakarta.ee website for the Specification Committee, Ivar to report back from his action from the 01/08 meeting

Tanja to report back on updates to the landing page.

See: https://jakarta.ee/committees/ and https://jakarta.ee/committees/specification/

  • Engaging and responsiveness of the spec projects. Are there responsive committers in all projects?

Kevin indicated that it is going reasonably well.

https://github.com/eclipse-ee4j/jakartaee-platform/issues/131

Related topic: Listing all versions of compatible products on the Compatible Products page (get listed page)

Document of discussion between Kevin and Paul at ECE on a related topic:

https://docs.google.com/document/d/1dWDXjtAlwxtmj1LT_mUvSceyU5J5_n1eJvwYO4fhPbM/edit

Discussion was had regarding listing product versions on the Compatible Products page and compatible implementations on the individual specification pages such as the Platform Specification. 

Proposal: (i) The Compatible Products page has only the most current version of the product listed. Company web pages can list as many versions as the care to. The process to add a product or new version of a product to the page is explained here.

The individual specification pages list up to 5 (or 10) major & minor version updates that are approved via the PR process described in the Spec Committee Operations document.

Note: The Foundation to be requested to update the product’s Proof of Certification link on the Compatible Products page to point directly to the “TCK results summary” in the Compatibility certification request PR instead of the PR.

  • Implementing clear statuses on the specification pages - See David’s proposal

    • First draft of a proposal to bootstrap discussion is here:
    • There is also a nice-to-have add-on:

  • Status on the approval for Jakarta EE 8 “Java SE” specs

https://github.com/jakartaee/specifications/pulls?q=is:pr+is:open+label:javase

  • Note: Approved by lazy consensus on the list - Preferred convention for use of class names in spec documents is consistency within a spec, that is all that is required

Back to the top