| <!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 #4</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 #4</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="#pmc-statement-about-quality-control">PMC Statement about Quality Control</a></li> |
| <li><a href="#licensing-concerns-for-implementation-projects">Licensing Concerns for Implementation Projects</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: 2018-01-16</p> |
| </div> |
| <div class="paragraph"> |
| <p>Present:</p> |
| </div> |
| <div class="ulist"> |
| <ul> |
| <li> |
| <p>Mark</p> |
| </li> |
| <li> |
| <p>Kevin</p> |
| </li> |
| <li> |
| <p>Dmitry</p> |
| </li> |
| <li> |
| <p>Wayne</p> |
| </li> |
| <li> |
| <p>Steve</p> |
| </li> |
| <li> |
| <p>David</p> |
| </li> |
| <li> |
| <p>Ivar</p> |
| </li> |
| </ul> |
| </div> |
| </div> |
| </div> |
| <div class="sect1"> |
| <h2 id="pmc-statement-about-quality-control"><a class="anchor" href="#pmc-statement-about-quality-control"></a><a class="link" href="#pmc-statement-about-quality-control">PMC Statement about Quality Control</a></h2> |
| <div class="sectionbody"> |
| <div class="paragraph"> |
| <p>Discussion about how to handle updates to transfered projects until the legal agreements between Oracle and Eclipse |
| have been signed. Outcome of discussion is that the PMC suggests that:</p> |
| </div> |
| <div class="ulist"> |
| <ul> |
| <li> |
| <p>the version to be released as the first release of “EE4J” which pass the Java EE 8 TCKs should be kept |
| in a separate <strong>protected</strong> branch.</p> |
| </li> |
| <li> |
| <p>this branch has to be named ee4j_8 to communicate the compatibility with Java EE 8</p> |
| </li> |
| <li> |
| <p>the master branch will be the next version, possibly version 9</p> |
| </li> |
| </ul> |
| </div> |
| <div class="paragraph"> |
| <p>Guidelines must be communicated to the community as soon as possible. |
| Eclipse and Oracle will provide the text to communicate.</p> |
| </div> |
| </div> |
| </div> |
| <div class="sect1"> |
| <h2 id="licensing-concerns-for-implementation-projects"><a class="anchor" href="#licensing-concerns-for-implementation-projects"></a><a class="link" href="#licensing-concerns-for-implementation-projects">Licensing Concerns for Implementation Projects</a></h2> |
| <div class="sectionbody"> |
| <div class="paragraph"> |
| <p>Discussion whether it makes sense to require the same license for implementation projects as for the API and spec projects.</p> |
| </div> |
| <div class="paragraph"> |
| <p>There is no requirement from Eclipse Foundation that subprojects follow the parent project. The PMC may allow sub-projects |
| deviate from the parent project licensing. We will look at this from case to case and if it becomes the norm, we will |
| revisit this item again.</p> |
| </div> |
| </div> |
| </div> |
| </div> |
| </body> |
| </html> |
