Hi Kevin,
Just wanted to add a further question. Am I right in saying that in regards to
https://github.com/jakartaee/specifications/pull/225 (The EL 4.0.0 PR), it can’t be merged of approved until the TCK is final?
Best regards,
Matt
From: jakarta.ee-spec.committee-bounces@xxxxxxxxxxx <jakarta.ee-spec.committee-bounces@xxxxxxxxxxx>
On Behalf Of Kevin Sutter
Sent: 21 July 2020 17:16
To: Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Subject: Re: [jakarta.ee-spec.committee] Mentoring specifications
Kenji,
You should reference the Platform TCK, both from a staging and final version perspective. You could also add text to the checklist entry to indicate that you are dependent on the Platform TCK.
---------------------------------------------------
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
From: "kzr@xxxxxxxxxxx" <kzr@xxxxxxxxxxx>
To: Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Date: 07/21/2020 11:10
Subject: [EXTERNAL] Re: [jakarta.ee-spec.committee] Mentoring specifications
Sent by: jakarta.ee-spec.committee-bounces@xxxxxxxxxxx
Let me make sure about TCK and certification request portions of the checklist.
If the specification has no standalone TCK and uses Platform TCK, what should we check ?
Or can we leave them as uncheck status ?
-Kenji Kazumura
From:jakarta.ee-spec.committee-bounces@xxxxxxxxxxx <jakarta.ee-spec.committee-bounces@xxxxxxxxxxx>
On Behalf Of Ivar Grimstad
Sent: Saturday, July 18, 2020 11:07 PM
To: Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Subject: [jakarta.ee-spec.committee] Mentoring specifications
Esteemed specification committee members,
The ballots for the first wave of specifications are scheduled to start on Monday 20th. You are probably all well underway reviewing the PRs for specifications to which you were assigned
as a mentor. I have compiled a short checklist for what needs to be done.
If a PR has been created for the specification
-
Assign yourself as a reviewer
-
Add a comment to the PR containing the checklist [1],
like Kevin has done for [2]
-
Start reviewing
-
[optional] Join the mailing list for the project producing the specification
-
[optional] It may be a nice gesture to send an email to the project mailing list explaining what you are doing. An example here [5]
If a PR has NOT yet been created for the specification
-
Check which wave it is in [3]
-
Check when the due date for the ballot start for that wave [4]
-
Join the mailing list for the project producing the specification
-
Send an email explaining your role as a mentor and ask if they are on track to make the due date for producing the PR
-
Follow up until a PR has been created, then start reviewing
[1] https://github.com/jakartaee/specification-committee/blob/master/spec_review_checklist.md
[2]
https://github.com/jakartaee/specifications/pull/225
[3]
https://eclipse-ee4j.github.io/jakartaee-platform/jakartaee9/JakartaEE9ReleasePlan
[4]
https://eclipse-ee4j.github.io/jakartaee-platform/jakartaee9/JakartaEE9#jakarta-ee-9-schedule
[5]
https://www.eclipse.org/lists/jaxws-dev/msg00031.html
Hope this helps.
Ivar
--
Ivar Grimstad
Jakarta EE Developer Advocate |
Eclipse Foundation, Inc.
Community. Code. Collaboration.
Join us at our virtual event:
EclipseCon 2020-
October 20-22_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee