Assign two “Release Owners” for each platform release.
One experienced (previous release) and one new.
Roll the responsibility among the project leads.
Part of the release planning is to decide if a spec is eligible for inclusion in the platform.
Plan review contains a list of candidate specs
Release review contains a list of included specs
Discussed the proposal with no objections other than updating it to be “two release owners”. We decided to discuss further on mailing lists to see if we can appoint the release owners.
Should we establish a release train for the platform?
Establish a release train with a 6-month release cycle. The release contains the specs that are ready, or else the previous version is included.
Discussed the proposal.
We decided that it is a good idea to start with Jakarta EE 9 and decide on the cadence for subsequent releases later as Jakarta EE 9 cannot be entirely date-driven due to the namespace change.
A proposal is to start with a 12-month cycle and reduce later.
Discuss this further in a GitHub Issue.
How do we track the content and progress of a release?
Use GitHub Projects. One board per release with the stages in the spec process as columns.