I think Bill Shannon added that step. You are right that is not required for Jakarta EE 8 release, but should be captured as a TODO post release.
Hi Scott,
I don’t think that we need to do the additional steps you are talking about. There are minor updates to the projects (javadocs and text files). In this case the release review is NOT required. Integrating new APIs to GlassFish should be done, but it doesn’t affect the Jakarta EE 8 schedule and can be done later. I am suggesting including it as a separate task.
Thanks, Dmitry
The JESP Ops guide has the full set of steps needed to complete a Jakarta release. There are some additional steps beyond the creation of the PRs against the spec committee repo that need to be done on the Eclipse dev process side of the house. These were not detailed in the single page set of steps at https://wiki.eclipse.org/How_to_Prepare_API_Projects_to_Jakarta_EE_8_Release, so I have added them after the current step to create the 2 PRs against the spec committee specifications repo.
Note that there is also a spreadsheet that leads should be keeping updated with the progress of a release. This has been updated to include these additional steps as well. That sheet is available here, and should be accessible by anyone with the link: _______________________________________________ jakartaee-spec-project-leads mailing list jakartaee-spec-project-leads@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
_______________________________________________ jakartaee-spec-project-leads mailing list jakartaee-spec-project-leads@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
|
