[IG] Decide which specifications to prune/deprecate.
Publish specific proposal(s) to Platform dev mailing list. Steve volunteered to organize the material and post for a “vote” by Platform Committers. The list should even contain items that has been decided.
[TO] Tanja to find out a list of committers on the Jakarta EE Platform Project and request them to sign up to the platform project mailing list.
We want it to be a requirement for committers to subscribe to the mailing list.
[KWS] Determine a dependency graph for the remaining projects and work out a spreadsheet (or some doc) of all of the pieces of required work.
Work with David Blevins on the dependency work that he did previously.
Based on previous discussions, the Jakarta EE Steering Committee provided the following guidance in the form of goals for the Jakarta EE 9 release. This project team needs to produce a plan that meets these goals by Dec 9. If we determine that there are technical reasons that a particular goal can not be met, we need to provide that feedback to the Steering Committee. The project plan needs to provide technical guidance to the many specification and implementation projects that will contribute to the Jakarta EE 9 release, and must determine whether sufficient resources are likely to be available to meet the Jakarta EE9 requirements on the proposed schedule.
Steering Committee, October 29, 2019:
RESOLVED, the Jakarta EE Steering Committee requests that the Jakarta EE Platform Project leadership deliver a Jakarta EE 9 Delivery Plan to the Steering Committee no later than December 9, 2019, for the Steering Committee to consider adopting as the roadmap for Jakarta EE 9, and that the Jakarta EE 9 Delivery Plan accommodates the following constraints:
implements the “big bang”
Includes an explicit means to identify and enable specifications that are unnecessary or unwanted to be deprecated or removed
Moves all remaining specification APIs to the Jakarta namespace
States that no new specifications are to be added, apart from specifications pruned from Java SE 8 where appropriate, unless those specifications clearly will not impact the target delivery date
The plan shall define a delivery date, and the team should view meeting the above requirements in as early a timeframe as possible as a higher priority than adding additional functionality to the release.