Scott, Yes. I am
in the process of creating separate "epic" github Issues for
each Specification Project with an embedded checklist. These Issues
will then be used for tracking progress via a github Projects board. Here's
an example of the Issue that I've been reviewing with Steve before I push
the button to create them across the board. Comments or suggestions
are welcome. Thanks!
--------------------------------------------------- Kevin Sutter STSM, MicroProfile and Jakarta EE architect @ IBM e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter phone: tl-553-3620 (office), 507-253-3620 (office) LinkedIn: https://www.linkedin.com/in/kevinwsutter
Stark <starksm64@xxxxxxxxx> To:
Spec Project Leadership discussions <jakartaee-spec-project-leads@xxxxxxxxxxx> Cc:
developer discussions <jakartaee-platform-dev@xxxxxxxxxxx> Date:
Re: [jakartaee-platform-dev] [jakartaee-spec-project-leads] Requesting
Release Records from all Specification Projects Sent
Should we have a EE9 github issue to
track the various project records, or some place where this can be validated
On Mon, Jan 13, 2020 at 1:31 PM Kevin
wrote: Hi, As a requirement of the Eclipse Development Process (and the Jakarta
EE 9 Release Plan),
we need all individual Jakarta
an Eclipse Release Record.
Since the majority of the Specification Projects are covered under
the umbrella Release Plan, all that is required is to create a simple Release
Record along the lines of what I did for the Jakarta
EE 9 release. Very simple TODO for the majority of the Jakarta Specification Projects.
Any committer on the Specification Project can do this creation.
The dates you enter are not "cast in stone", but since we're
shooting for a June release for the Platform, do not enter a release date
beyond June 2020. There are a couple of projects that need a bit more work... Jakarta
Enterprise Beans and
slight modifications beyond what is specified in the Jakarta EE 9 Release
Plan. For these cases, a more elaborate Eclipse Release Record is
required. I would suggest still referencing the Jakarta EE 9 Release
Plan, but then also add details on the required updates right in the Release
Record. These individual Release Records/Plans will need to reviewed
with the Specification Committee at your earliest convenience. Any other Specification Projects that are planning to go beyond the Jakarta
EE 9 Release Plan will also need to follow the same process as Enterprise
Beans and Activation. Maybe Restful
into this camp? Others? Thanks for your help!