Community
Participate
Working Groups
We'll use this bug to track the release We require IP Team approval of the IP Log. We require PMC approval of the release and review materials.
Note that, at present, we do not have an agreement in place with Oracle to use the javax namespace, so we're limited in terms of what we're allowed to do. At present, the publication of binary artifacts which include changes (or additions) to APIs in the javax namespace cannot be made available for general use. Before we can declare success on this release review, we'll need the PMC to validate that the release does not include changes or additions to APIs in a javax namespace.
The IP Log is approved.
(In reply to Wayne Beaton from comment #1) > Note that, at present, we do not have an agreement in place with Oracle to > use the javax namespace, so we're limited in terms of what we're allowed to > do. At present, the publication of binary artifacts which include changes > (or additions) to APIs in the javax namespace cannot be made available for > general use. AFAICT, the 2.1.1 version is built from the EE4J_8 branch which only includes edits to documentation. I'm confident that the terms of the agreement are being respected. Thanks Markus.
Exactly, this is identical to 2.1 module some bug fixes. It is similar to the 1.1.3 release version of JSONP: https://projects.eclipse.org/projects/ee4j.jsonp/releases/1.1.3
PMC approval: https://dev.eclipse.org/mhonarc/lists/ee4j-pmc/msg00835.html
I have scheduled this review to conclude on September 5, 2018.
I declare this review successful! Please continue with your release.
