Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jakarta.ee-wg] Minutes of Oct 9 Jakarta EE Steering Committee Meeting

Minutes of October 9 Jakarta EE Steering Committee Meeting

 

The Zoom ID for the remainder of 2018 is:

https://eclipse.zoom.us/j/499849869 

Attendees (to be confirmed):


Fujitsu: Kenji Kazumura, Mike Denicola
IBM: Kevin Sutter, Dan Bandera
Oracle: Will Lyons
Payara: Steve Millidge
Red Hat: Mark Little
Tomitribe:  David Blevins, Richard Monson-Hafael
Martijn Verburg
Ivar Grimstad

Eclipse: Mike Milinkovich

 

Review of Minutes from Prior Meeting 

 

The minutes of the Sept 25 meeting were approved.

Budget Update 

 

The Eclipse Foundation has distributed participation agreement to all Strategic Members with exception of Fujitsu.

A similar process will occur with participant members, to be initiated at end of October.

Working Group Calls

 

Weds @11 AM Eastern time been selected and Doodle notification has been sent.  Calls will be set up on a monthly basis beginning mid November and communicated to the Working Group.  

EclipseCon Europe 

 

No significant updates.

 

Updates on Oracle contributions

 

https://www.eclipse.org/ee4j/status.php

Working to following schedule:

        Sep 21 -- All code required for GF build contributed.
        Sep 23 — Eclipse GlassFish builds.
        Oct 1 -- Java EE 8 CTS testing. We are able to run CTS tests on Eclipse GlassFish.
        Oct 22 — CI/CD release pipelines completed.
        Oct 22 -- Eclipse GlassFish 5.1-RC1 milestone release.
        Nov 5 — Dependencies updated. All projects are released to OSSRH and have dependencies to Eclipse version of other components.
        Nov 30 -- Release Review completed.
        Dec 14 -- Eclipse GlassFish 5.1 release. All CTS tests are passed.

 

Oracle has blogged on the above:

https://blogs.oracle.com/theaquarium/moving-forward-with-eclipse-glassfish-at-jakarta-ee
 

Nightly builds are available from the Jenkins Ci/CD system:

https://jenkins.eclipse.org/glassfish/job/glassfish-nightly-freestyle/lastSuccessfulBuild/artifact/appserver/distributions/glassfish/target/glassfish.zip

https://jenkins.eclipse.org/glassfish/job/glassfish-nightly-freestyle/lastSuccessfulBuild/artifact/appserver/distributions/web/target/web.zip

 

We will archive the RC build that is generated for our Oct 22 Milestone.

 

Discuss Building Momentum for Jakarta EE discussed in the last Steering Committee meeting (excerpts from email content in italics)

 

1. Release Eclipse GlassFish and certify it as Java EE 8 compatible.

Each of the EE4J projects have project leads identified.   Each of the EE4J projects needs to be released and a task in the project’s issue tracker has been opened to track this activity.   For example, see: https://github.com/eclipse-ee4j/servlet-api/issues/195  

We would welcome project leads, or other committers, to take the initiative to:
•    Review the release documents and prepare to release these projects, or recruit and encourage other community members to do so, and..
•    Update the appropriate Jira issues reflecting your plans
•    Let Ed and Dmitry know if you will take on responsibility for releasing the project in question

Dmitry has created a Google spreadsheet for tracking progress:
https://docs.google.com/spreadsheets/d/1e8inaprMOjnq04hU2o76egHhC8AF3-vNvqjRq6GR0eM/edit#gid=0

 

There has been significant progress on initiating and completing CI/CD pipeline tasks. The following is a status summary:

- Number of projects with pipeline tasks complete: 37

- Number of projects with pipeline tasks in progress: 71

- Number of projects with pipeline tasks not started: 11

2. Create a roadmap for definition of a specification process by the end of the year

  Ideally we will define public milestones some of which are achievable by Code One / EclipseCon Europe.  

Hope to approve community draft version of the spec process doc on October 9, for Steering Committee approval on October 16.    The intent is for the community draft version to be submitted for community review and feedback on mailing list and on Google doc (comments only).   Feedback instructions will be provided.  

3. Announce commitment to Working Group funding

Assuming we collectively commit to a funding model, we should communicate this externally.   We expect to make progress on this topic in the next Steering Committee meeting.

 

Mike has blogged on this. Complete.

4. Demonstrate successful execution of the contributed TCKs

Progress on this is possible by Code One/ECE but not likely.  Our messaging should not rely on this.

 

Need approvals to begin process of building from contributed source.   Will attempt execution.   Check-in on this at the Oct 16 Steering Committee meeting.

5. Define distributed ownership of Jakarta EE technology areas and directions

This is related to item #1.

 

6. Commit to Code One/ECE messaging

    https://docs.google.com/document/d/1_Bgh5rP1qKJdATlQ5ZC-ceJ9AFvHq8lq8_xFrarnlH0/edit


I will update to align with Mike's blog on funding/blogging.

Assuming the specification process is still on track, I will update this document to reflect that.

Regarding setting technical direction, update from the community discussion on Jakarta EE technology directions which David has initiated. 

David put out a more specific doc October 8.   Requests that all SC members comment on the doc at:
https://docs.google.com/document/d/1y-Vs4d9Iotw0HqsiTxG5UCm7ua0w35vJZkGVmS_hFrw/edit

 

DEADLINE for inclusion any officially prepared Working Group statements:  Friday, October 12th, 11pm Pacific

 

(David will summarize - we will review this at the Oct 16 Steering Committee meeting)


DEADLINE for realistic inclusion any third party Jakarta EE news coverage  Friday, October 19th, 11pm Pacific  (Feedback on 10/12 is preferred, will be difficult to include anything controversial if input received after Oct 12)

Code One/ECE presence

  

Mark has a panel discussion scheduled:   Simon Maple chair, David, Mark, Ivar, Ian, Will, will seek to include JUG reps.   Mark will define how we seed questions.

If you are attending Code One, you should have received an invitation to The Thirsty Bear event.  Check for mail from Ed Bratt: 

[jakarta.ee-spec.committee] Invitation: CodeOne Event: Next Big Thing (Thirsty Bear) event

Legal Documents  

 

Oracle Legal is working on the TM license agreement. We have requested a date for a draft.

Marketing Committee Update

 

Regarding standardization of project pages – the existing thread should be discussed offline.   Tanja will forward.   Request that Ed and Bill follow up with Tomitribe contact and report back on this topic with a proposal/plan at a meeting following ECE/Code One.

PMC Update

Discussed standards for module names, will post on GitHub for community input.   

PMC will take input, come to community consensus, and make a recommendation for spec committee, steering committee and EMO review.


Back to the top