The committer teams need to review the staged TCK content and give their
+1 for the relevant TCK bundle to be promoted. The promotion will
freeze the TCK for release, which essentially means it is frozen. If a
blocking change in a TCK is needed, we will re-release with a
incremented version number as mentioned below.
The possible states that TCKs can transition through are:
* Staged via
https://download.eclipse.org/ee4j/jakartaee-tck/jakartaee9-eftl/staged-900
(each TCK zip may be updated multiple times).
* Promoted via
https://download.eclipse.org/ee4j/jakartaee-tck/jakartaee9-eftl/promoted
(each versioned TCK zip is frozen immediately, further changes can only
appear via a version number increment).
* Final release for Jakarta EE 9 via
https://download.eclipse.org/jakartaee/...
On 7/27/20 11:21 AM, Ed Bratt wrote:
> Due to how the Specification Committee has defined the process, any
> change to the TCK requires are re-release -- Docs. change, Exclude List
> change, anything else that would change content and/or generate a build
> forces a version number increment.
>
> I think the procedures described below will allow us to stop builds,
> once a Specification has gone to ballot. So, that's my first concern. We
> just need to follow the ballot progress closely and not inadvertently
> create an update that wasn't asked for.
From a process point of view, I think that the SPEC API
representative/lead/committers can help determine when it is time for
the relevant TCK to transition from Staged to Promoted state.
Question, if we don't hear feedback from a SPEC lead or committers, who
can make the decision to proceed with Promoting the TCK? Also how long
should we wait for feedback?
There is no perfect amount of time to wait for feedback, if we make it too short, we may need to stage/promote a newer standalone TCK version for further changes. If we make it too long, we may never hear feedback and could jeopardize the EE 9 schedule.
I'm thinking that we can wait a few days after pinging the SPEC API teams (whether it is sending email or pinging lead(s)).
Worse case, we could later stage a jakarta-annotations-tck-2.0.1.zip if further TCK pull requests for documentation changes are important.
Scott
Good news, it is now time for Staged jakarta-annotations-tck-2.0.0.zip
to be reviewed via
https://github.com/eclipse-ee4j/jakartaee-tck/issues/382. Feedback is
welcome (link to staged TCK zip is in the issue)!
Also good news, it is now time for Staged
jakarta-_expression_-language-tck-4.0.0.zip to be reviewed via
https://github.com/eclipse-ee4j/jakartaee-tck/issues/387.
Once the relevant SPEC API lead and/or committers has given their
approval via the relevant jakartaee-tck issue, we will Promote the
related TCK.
We have created some other similar "Review and promote " tracking issues
for other TCKs but help is needed to created tracking issues for other
TCKs still (open
https://github.com/eclipse-ee4j/jakartaee-tck/issues?q=is%3Aissue+is%3Aopen+Review+and+promote
for current issues).
Scott
