Thank Jan for spotting the email address typo! I have reviewed and merged your PR. In order to address Ed's and your suggestions regarding improving the tck process, I have opened this issue so that we can discuss further for our 2nd version. The important bit is to get the first version out of the door so that we have something to rely on.
I will leave this ballot open for one more day so that you can all take a look at the doc again with the typos and formats fixed. I will conclude this ballot tomorrow (super-majority +1 received) unless I hear otherwise.
Thank you all for your review and support on this matter!
Additionally, following Ed's concerns
I think we should wait for the results of the ongoing
discussions in Jakarta EE which might affect us in MicroProfile
too.
Even when there are significant
differences as we have one version and one namespace for all
relevant artefacts (spec document, API, TCK) of a component spec
and they all stored in Maven already.
I think we need some of the results
(including open legal questions) to have a final version here -
and we have the time to do it.
Of course, an update could solve this
aspect in the future too...
But the wrong email address need to
be fixed at least now on my opinion.
Does anybody has the source of that
file, which can be edited?
Otherwise I can offer to redraw it
using BPMN and convert it to SVG to be included (but editable in
the future).
Best, Jan
Am 15.02.22 um 20:54 schrieb Ed
Bratt:
+1 (Oracle)
For the next review/update of this process, I'd like to make
the following observations:
Packaging requirements: Jakarta EE is struggling with
the requirement that forcing the ancillary (supporting
documentation, guides, coverage, and assertion documents) into
the TCK binary is problematic for publication to central
repositories such as Maven central. We are currently working
on an effort to update the packaging aspect of these
requirements. MicroProfile may want to consider updates along
these lines itself, or perhaps wait until after Jakarta EE
determines what changes it will allow and then follow suit.
Test changes in Service Releases
The very final clause of the document (that service releases
'... may have test changes...') might be considered for update
in a future revision
In the past, we tried to adhere to the rule -- Once a test is
formally adopted, it cannot change -- If the Spec. dev. team
receives a challenge and it feels that a specific test must
remain but the test must be altered, we allowed that an Alternative
test could be provided in the TCK. If an alternative is
offered the vendor could choose to run the original test, or
the alternative test and they are considered equivalent for
the purposes of compatibility verification. The goal was
existing tests cannot be changed in anything less than a minor
release. Successfully challenged tests may be excluded OR,
they may remain and either the original or the alternative may
be chosen by the vendor.
Alternative tests were rarely utilized. The decision to
provide an alternative test or simply exclude that test would
be at the discretion of the Spec. development group. Allowing
a general assertion like this seems difficult to manage, in my
opinion. I would discourage groups from attempting to change
the TCK tests themselves in service releases.
Thank you,
-- Ed Bratt
On 2/9/2022 3:10 PM, Emily Jiang
via microprofile-wg wrote:
As agreed on yesterday's MicroProfile Technical call, I
have now merged the PR of MicroProfile TCK Process from
David and myself. The TCK process can be viewed from here.
To approve and ratify the MicroProfile TCK Process, the
Steering Committee Representatives' vote is requested.
Please respond with +1 (positive), 0 (abstain), or -1
(reject). Any feedback that you can provide to support
your vote will be appreciated.
According to MicroProfile
Specification Process, This ballot runs for seven days
and ends on February 16th. The ballot requires a
Super-majority positive vote of the Steering Committee
members. There is no veto. Community input and Community
votes are welcomed. However, only the votes delivered by
Steering Committee Representatives will be counted.
--
Thanks
Emily Jiang on behalf of MicroProfile Steering
Committee