Mike Milinkovich wrote on 05/30/18 02:59 PM:
Bill Shannon:
- ... we were previously expecting that a specification
project would manage the specification document, the source
code for the API classes, and the source code for the TCK.
Assuming we need special rules for specification projects, do
we really want those special rules to apply to the API and
TCK, which after all are just source code projects?
- ... The API classes are hard because they mix specification
with (varying amounts of) implementation. But none of the IP
issues for the spec apply to the TCK, right? Maybe the TCKs
should be in separate code projects that follow the normal EDP
rules?
- Proposed Resolution:
- The definition of a Specification Project should be
refined to recognize that the Specification Document and the
TCK will be done in separate Eclipse project managed under
the same PMC.
I guess that means we'll need to propose separate Eclipse projects
for the TCKs. In the short term this means a few more projects for
the soon-to-be-submitted separate TCKs, and in the long term many
more projects for the TCKs that are split off from the CTS.
|
