| <!DOCTYPE html> |
| <html lang="en"> |
| <head> |
| <meta charset="UTF-8"> |
| <!--[if IE]><meta http-equiv="X-UA-Compatible" content="IE=edge"><![endif]--> |
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> |
| <meta name="generator" content="Asciidoctor 1.5.6.1"> |
| <title>EE4J PMC Meeting #2020-06</title> |
| <style> |
| |
| </style> |
| <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.6.3/css/font-awesome.min.css"> |
| </head> |
| <body class="article toc2 toc-left"> |
| <div id="header"> |
| <h1>EE4J PMC Meeting #2020-06</h1> |
| <div id="toc" class="toc2"> |
| <div id="toctitle">Table of Contents</div> |
| <ul class="sectlevel1"> |
| <li><a href="#general">General</a></li> |
| <li><a href="#set-source-and-target-level-in-parent-pom">Set source and target level in parent POM?</a></li> |
| <li><a href="#release-qualifiers">Release Qualifiers</a></li> |
| <li><a href="#copyright-headers-clarification">Copyright Headers Clarification</a></li> |
| <li><a href="#ee4j-top-level-web-page">EE4J Top Level Web page</a></li> |
| <li><a href="#jakarta-ee-9-project-management">Jakarta EE 9 project management</a></li> |
| </ul> |
| </div> |
| </div> |
| <div id="content"> |
| <div class="sect1"> |
| <h2 id="general"><a class="anchor" href="#general"></a><a class="link" href="#general">General</a></h2> |
| <div class="sectionbody"> |
| <div class="paragraph"> |
| <p>Date: 2020-06-02</p> |
| </div> |
| <div class="paragraph"> |
| <p>Present:</p> |
| </div> |
| <div class="ulist"> |
| <ul> |
| <li> |
| <p>Kevin Sutter (IBM)</p> |
| </li> |
| <li> |
| <p>Mark Little (Red Hat)</p> |
| </li> |
| <li> |
| <p>Ed Bratt (Oracle)</p> |
| </li> |
| <li> |
| <p>Dmitry Kornilov (Oracle)</p> |
| </li> |
| <li> |
| <p>Kenji Kazamura (Fujitsu)</p> |
| </li> |
| <li> |
| <p>Steve Millidge (Payara)</p> |
| </li> |
| <li> |
| <p>Ivar Grimstad (Eclipse Foundation)</p> |
| </li> |
| </ul> |
| </div> |
| </div> |
| </div> |
| <div class="sect1"> |
| <h2 id="set-source-and-target-level-in-parent-pom"><a class="anchor" href="#set-source-and-target-level-in-parent-pom"></a><a class="link" href="#set-source-and-target-level-in-parent-pom">Set source and target level in parent POM?</a></h2> |
| <div class="sectionbody"> |
| <div class="paragraph"> |
| <p>See <a href="https://github.com/eclipse-ee4j/ee4j/issues/59" class="bare">https://github.com/eclipse-ee4j/ee4j/issues/59</a></p> |
| </div> |
| <div class="paragraph"> |
| <p>Discussed and agreed to encourage the submitter of the issue to submit a PR.</p> |
| </div> |
| </div> |
| </div> |
| <div class="sect1"> |
| <h2 id="release-qualifiers"><a class="anchor" href="#release-qualifiers"></a><a class="link" href="#release-qualifiers">Release Qualifiers</a></h2> |
| <div class="sectionbody"> |
| <div class="paragraph"> |
| <p>Following up the discussions on the mailing list regarding release qualifiers. |
| The vote for different formats only resulted in three votes so far.</p> |
| </div> |
| <div class="ulist"> |
| <div class="title">The PMC suggests the following format:</div> |
| <ul> |
| <li> |
| <p>x.y.z-[Bn|Mn|RCn]</p> |
| </li> |
| <li> |
| <p>Upper case, hyphen, no dot after the version number..</p> |
| </li> |
| </ul> |
| </div> |
| <div class="paragraph"> |
| <p>Kevin will update the version document.</p> |
| </div> |
| </div> |
| </div> |
| <div class="sect1"> |
| <h2 id="copyright-headers-clarification"><a class="anchor" href="#copyright-headers-clarification"></a><a class="link" href="#copyright-headers-clarification">Copyright Headers Clarification</a></h2> |
| <div class="sectionbody"> |
| <div class="paragraph"> |
| <p>This comes up periodically. Example:</p> |
| </div> |
| <div class="paragraph"> |
| <p>A file has the following header</p> |
| </div> |
| <div class="listingblock"> |
| <div class="content"> |
| <pre class="highlight"><code>Copyright (c) 2009, 2018 Oracle and/or its affiliates. All rights reserved.</code></pre> |
| </div> |
| </div> |
| <div class="paragraph"> |
| <p>After it is modified, this is how it should be:</p> |
| </div> |
| <div class="listingblock"> |
| <div class="content"> |
| <pre class="highlight"><code>Copyright (c) 2009, 2020 Oracle and/or its affiliates and others. All rights reserved.</code></pre> |
| </div> |
| </div> |
| <div class="paragraph"> |
| <p>Full description in the Eclipse Development Handbook.<br> |
| Ivar will update the wiki if needed.</p> |
| </div> |
| </div> |
| </div> |
| <div class="sect1"> |
| <h2 id="ee4j-top-level-web-page"><a class="anchor" href="#ee4j-top-level-web-page"></a><a class="link" href="#ee4j-top-level-web-page">EE4J Top Level Web page</a></h2> |
| <div class="sectionbody"> |
| <div class="paragraph"> |
| <p>Discussed that we lack an easy way to find the various EE4J project’s web sites.</p> |
| </div> |
| <div class="ulist"> |
| <div class="title">Specification Projects (Jakarta EE):</div> |
| <ul> |
| <li> |
| <p>All specifications are listed here: <a href="https://jakarta.ee/specifications/" class="bare">https://jakarta.ee/specifications/</a></p> |
| </li> |
| <li> |
| <p>There is a link to the project producing the specification on each specification page<br> |
| Example:</p> |
| </li> |
| </ul> |
| </div> |
| <div class="imageblock"> |
| <div class="content"> |
| <img src="./images/platform.png" alt="platform"> |
| </div> |
| </div> |
| <div class="ulist"> |
| <ul> |
| <li> |
| <p>The <a href="https://projects.eclipse.org/projects/ee4j.jakartaee-platform">Project</a> link points to the Project’s PMI page.</p> |
| </li> |
| <li> |
| <p>The <a href="https://eclipse-ee4j.github.io/jakartaee-platform/">Website</a> link points to the Project’s website. Will only be displayed if the link is provided by the project in their PMI settings:</p> |
| </li> |
| </ul> |
| </div> |
| <div class="imageblock"> |
| <div class="content"> |
| <img src="./images/platform-pmi.png" alt="platform pmi"> |
| </div> |
| </div> |
| <div class="ulist"> |
| <div class="title">Regular Projects (EE4J):</div> |
| <ul> |
| <li> |
| <p>All implementation projects are listed on the EE4J PMI page<br> |
| <a href="https://projects.eclipse.org/projects/ee4j" class="bare">https://projects.eclipse.org/projects/ee4j</a></p> |
| </li> |
| <li> |
| <p>If a project has a website configured (see above), the link is provided under Project Links in the right-menu.</p> |
| </li> |
| </ul> |
| </div> |
| <div class="ulist"> |
| <div class="title">Decided to:</div> |
| <ul> |
| <li> |
| <p>Create gh-pages website for EE4J Top Level Project</p> |
| </li> |
| <li> |
| <p>Should contain an Index of all project websites (gh-pages or others) for the projects</p> |
| </li> |
| </ul> |
| </div> |
| </div> |
| </div> |
| <div class="sect1"> |
| <h2 id="jakarta-ee-9-project-management"><a class="anchor" href="#jakarta-ee-9-project-management"></a><a class="link" href="#jakarta-ee-9-project-management">Jakarta EE 9 project management</a></h2> |
| <div class="sectionbody"> |
| <div class="ulist"> |
| <ul> |
| <li> |
| <p>Milestone release focused on Platform and Web Profile artifacts (Spec, API, TCK, and CI)</p> |
| </li> |
| <li> |
| <p>Individual components (ie. Annotations, or Activation, …) are strongly encouraged to provide PRs for the Specifications repo, but these will not be a requirement for the Milestone release</p> |
| </li> |
| <li> |
| <p>These component PRs can include their artifacts in whatever state they think is consumable. For example, if the Spec is not available yet in pdf or html format, then skip those entries in the _index.md file. Providing the artifacts via Maven coordinates is also optional at the Component level (they are required at the Platform level).</p> |
| </li> |
| <li> |
| <p>These PRs should be very easy to create, review, approve, and merge. We’re looking for progress, not perfection. All members of the Spec Committee will need to watch for PRs that need reviewing and approving prior to our June 12 deadline.</p> |
| </li> |
| </ul> |
| </div> |
| </div> |
| </div> |
| </div> |
| </body> |
| </html> |
