| [ee4j-pmc] EE4J Releases and Release Reviews |
| Hi, Coming back to release reviews and releases topic. Last weeks I was working on projects dependencies graph. This work is finished now (in the first approximation). The image is attached. As you see, the graph is quite complex and has some circular dependencies. I see that we have two options how to deal with it: 1. Review and release project artifacts. It’s what Microprofile is doing. It’s complicated because of the dependencies graph complicity. I managed to unwind it and made a table with projects/artifacts release order. See here: https://docs.google.com/spreadsheets/d/1RR-Tz107wWoZw7TT74Ufy6gHQ4BMQ4qHksx_dY6pQpw/edit?usp=sharing. We may need to increase projects granularity to remove circular dependencies and make the whole process a bit easier. I am not proposing doing it now, it can be done later, after the first Jakarta EE release. 2. There are no problems with API projects and projects with easy resolvable dependencies like JSONP. We should apply for release review and release them asap. Projects with circular dependencies require more than one release though. The first release is as they are now with minor/minimal changes and no changes in dependencies. Dependencies to released EE4J projects are updated in future minor releases. Release review is needed only for the first release which eliminates problems dealing with dependencies hell. I cannot say that I like this option, but is easier than the first one. We need to decide what is the recommended way to go. In the meantime we can ask projects with no dependencies to apply for release reviews. Thanks, Dmitry  |