|Re: [ee4j-community] JCP and existing specs|
There is a very good reason to do so. IMHO the JCP is -still- the sole standardization organization which is allowed to publish official industrial standards bearing the word "Java" in the standard's name. Oracle has not yet officially announced its will to change that. Eclipse is just the place where we all work together to develop the content of these specs (spec text, APIs, RIs, TCKs), but at the end, it is -still- up to the JCP to accept it as an official standard. Hence the Eclipse projects will do "code first" approach and ask the JCP for official standardization afterwards. This "separation of concerns" also is what the EE4J PMC and Mike Milinkovic told me at EclipseCon Europe 2018, and I doubt it has changed since. So the EE4J PMC simply serves as the new spec lead in the JSRs, and fulfils all duties like organizing the expert groups (= the EE4J Subprojects) and filing the needed paperwork.
I'd say "none"? :)
On Thu, Nov 30, 2017 at 12:58 PM, Guillermo GonzÃlez de AgÃero <z06.guillermo@xxxxxxxxx> wrote:
Maintenance releases are not allowed until everything has been moved to Eclipse (at least that's what we were told these days when asking for a Security API MR). At that point, and if we finally decide to move away the JCP, what would be the reason to do MRs there?
Guillermo GonzÃlez de AgÃero
El jue., 30 nov. 2017 a las 19:46, Leonardo Lima (<leomrlima@xxxxxxxxx>) escribiÃ: