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

Hi All,

I got comments that a link to our live document with notes from Specification Committee would be easier to follow, so sending this link with a few minor changes.

Hope this is helpful,

Tanja

On 2019-01-24 4:29 p.m., Tanja Obradovic wrote:

Hello All,

can you please review for approval on out next call?

Spec Committee Meeting Minutes January 23rd, 2018

Attendees (present in bold):

Kenji Kazumura - Fujitsu, Michael DeNicola

Dan Bandera - IBM, Kevin Sutter, Alasdair Nottingham

Bill Shannon - Oracle, Ed Bratt, Dmitry Kornilov, Jim Wright, Will Lyons

Steve Millidge - Payara, Arjan Tijms

Scott Stark - Red Hat, Mark Little

David Blevins - Tomitribe, Richard Monson-Haefel

Ivar Grimstad - PMC Representative

Alex Theedom - Participant Member

Werner Keil - Committer Member

Antoine Sabot-Durand - Red Hat (CDI spec Lead)


Eclipse Foundation: Wayne Beaton, Tanja Obradovic


  • Past business / action items

    • Approval of Meeting min Jan 16th

    • Kevin moved, Scott second, no objections - minutes approved

  • Jakarta EE Town Hall call for the community

    • We’ll use Jakarta EE Working Group timeslot, Jan 30th @ 11AM EST

      • Review of 2018

      • Look ahead

    • Panel participation

      • Mike M., Kevin, David, Dmitry, Ivar, Dan

      • Heiko Rupp, MC

    • Agenda

      • Mike M. will do a presentation addressing review of 2018 and next steps, ~30min

      • Ivar / Tanja will prepare How to get involved and share with the Community, ~10min

      • Q&A from the audience, ~ 20min

  • Java EE Specification Documents contribution from Oracle

    • Oracle will transfer the rights of the specs they own, to Eclipse Foundation, pending JCP agreement

    • Expecting others to consider and respond

    • Separate legal agreement will be sent to others involved in Java EE specs

  • TCK process - David Blevins

    • CDI TCK process and  Bean Validation TCK process - Red Hat, Scott Stark, Antoine Sabot-Durand

    • Refer to email “Understanding the Current Specification Process” and Understanding Java EE TCK Process

    • Understanding MicroProfile TCK Process - Kevin Sutter, please review for discussion in the New Year

    • Java Batch TCK process - Kevin provided quick summary

      • The Java Batch TCK uses both JUnit and Test NG annotations.  You can use either one. There is a thin utility layer (SPI) that can be used to detect a "job completed" event.  Otherwise, the default mechanism is polling. I mentioned on the call that the TCK was then "thrown over the wall" to Oracle for integrating with the overall CTS bucket.  Although that was a valid statement, I now understand that we also had to some glorified find/replace transformations on the tests to make them ready for CTS. For example, the CTS bucket couldn't handle JUnit's Assert library, so that usage had to be scrubbed before delivering to CTS.  But, the actual integration of the TCK bucket into CTS was done by Oracle. As far as tracking challenges with the Java Batch TCK, this was done via github Issues.

    • TCK project nightly builds - once jakarta.ee/project pages are available it will be linked from there

      • Templates for project pages still in works

    • Completion of the TCK process no later than Jan 30th 2019

    • The topic of distribution of TCK via Maven Central was discussed

      • Compiled ZIP files can also be distributed via EF downloads server.

      • Some of these TCKs are quite large and are produced several times a year, so Sonatype may not be happy with us.

      • May consider using EF hosted Nexus instance

      • Do we need consumers to explicitly agree to any terms to get access to the TCK for a Ratified Final Specification? (e.g. some sort of click through)

        • “We gotta have an audit trail” - Dan Bandera

  • Jakarta EE 8 release

    • EF will be further working on identifying the work on the projects that can be done at this point

  • Jakarta EE Spec process and Jakarta EE NoSQL project

    • based on EFSP v1.0, but not necessarily the same

    • We will use  Jakarta EE NoSQL to test  EF Spec Process and do customization if necessary to create Jakarta EE Spec Process.By going through the process with Jakarta EE NoSQL, we will capture notes and evolve a draft of the Jakarta EE Specification Process.

    • Jakarta EE NoSQL provisioning is next step; we are waiting on :

      • Board approval of the new IP policy (DONE)

      • Agreements need to be in place (MCCA and WGPA) for project lead/primary committer (Tomitribe)

      • Agreements for other committers (being pursued by the EF Membership Team via separate channels).

      • Werner - update on Jakarta EE NoSQL

        • Nothing to add. We’re waiting on agreements to be signed. Hopefully we’ll have what we need in 2019Q1. There is effectively zero chance that we will be able to bootstrap NoSQL in 2018.

    • The equivalent of a JCP maintenance review needs to be addressed (additional notes Nov 28th)

      • Please refer to Maintenance Reviews email thread.

    • We need a “Dials and knobs” document (possibly an FAQ) that details how a Working Group might extend the EFSP.

      • Suggestion to describe what is immutable.

  • Jakarta EE Working Group calls

  • Jakarta EE road map

    • Platform Project team is looking into this

Many thanks!

--

Tanja Obradovic

Jakarta EE Program Manager | Eclipse Foundation, Inc.

Twitter: @TanjaEclipse

Eclipse Foundation: The Platform for Open Innovation and Collaboration

--

Tanja Obradovic

Jakarta EE Program Manager | Eclipse Foundation, Inc.

Twitter: @TanjaEclipse

Eclipse Foundation: The Platform for Open Innovation and Collaboration



Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com


Back to the top