Tom, Is JTA planning
some additional updates beyond the content of the Jakarta EE 9 release
plan? If not, then no additional review is required for JTA. The
overall Platform release review sufficed for all components that are not
going beyond the basic direction defined by the Jakarta EE 9 release plan.
There is really
no requirement that the release dates for wave 1 need to be prior to wave
2, prior to wave 3, etc. All projects should drive towards the earliest
possible release dates for their components. We are pushing for early
RC deliveries for the APIs so that other dependent components can continue
development. But, the final releases do not have to be done in "wave
Since each component
will be doing a major version upgrade, it is probably best to use the Type
B IP Due Diligence. As an example, for MicroProfile, we use Type
B for our major versions, and Type A for our minor versions.
--------------------------------------------------- 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
Jenkinson <tom.jenkinson@xxxxxxxxxx> To:
Spec Project Leadership discussions <jakartaee-spec-project-leads@xxxxxxxxxxx> Cc:
developer discussions <jakartaee-platform-dev@xxxxxxxxxxx> Date:
Re: [jakartaee-spec-project-leads] Requesting Release Records from all
Specification Projects Sent
Do we need to schedule a release review
for the release record at this time too?
Would it be possible that the different
waves be guided as to when would be appropriate to set for their release
On Mon, 13 Jan 2020 at 19:31, Kevin Sutter
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!