[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[jakarta.ee-spec.committee] Two TCK issues for committee discussion
|
On the additional working group call it was brought up that we have two holes in the TCK process that need to be addressed in the weekly spec call are:
1. How long after a TCK release does one need to certify new implementations against that version. I cannot find the equivalent terms in the JCP or JSPA, so perhaps it is part of the TCK license. It seems that I have a vague recollection of a requirement that new major implementation releases had to certify against the latest version of the associated TCKs. I suppose the community interest to serve is having implementations synch against the latest TCK periodically.
2. What changes are allowed in a given TCK minor release and when/how are new tests added to a TCK.
There were two somewhat opposing views here.
a. Try to add tests that improve coverage as soon as they are available. The tension here was not wanting to have new tests that could expose implementation choices as flaws when they were just interpretation differences. One option would be to have such tests as optional until the next rev of a spec. More frequent spec service releases could help here.
b. Only add tests when there are updates to the specs. There could be interim builds of the TCKs that could make new tests available in nightly builds of the TCK, but it was pointed out that there needs to be separation of tests that are known to be improving test coverage without adding new features vs tests that could be part of ongoing new spec development. Branching strategies can be used to separate the builds.
