A number of our spec leads/previous Java EE EG members have been asking about how the specs would resume work once the JESP was completed. Their questions bring up some questions regarding how the new Jakarta EE spec projects become fully functional.
An example of one question was whether the current Java EE specification projects are going to have any of the post EE 8 open issues migrated over to their Jakarta EE counterpart? One example is:
where there are references to previous Java EE specification text, and design discussions are happening. Given that such issues have not simply been moved over to the
https://github.com/eclipse-ee4j/jta-api/issues Jakarta EE project, the question was what restrictions if any would there be for interested parties to reconstitute such issues in the new Jakarta EE project?
There was a PMC statement about initial EE4J project contributions:
That outlines a number of project process level details that are not captured in the current JESP operations document. The questions that were raised by a previous JAX-RS EG member was in regard to a PR:
That was proposing a change to a public API that while made sense, would basically change the behavior for some edge cases.
The PMC statement suggests that only critical bugs should be fixed and incorporated into the EE4J_8 branch that is the basis for the Jakarta EE 8 platform release.
Our EG member was questioning what process was being used to mange the changes going into the EE4J_8 branch as there have been javadoc modifications mentioning a specific behavior which was vague before, and there was validation by a TCK. They were looking for a detailed guideline on what is allowed and what is not, which could be circulated to the project committers.
It seems like we need a bootstrapping section in the operations guide that deals with these types of questions as well as others I have gotten regarding specification text, unavailable TCKs like JAXB, etc.
Unless the initially approved JESP and related content is able to address existing issues, we don't see we are ready to approve a JESP.
