[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakarta.ee-spec.committee] TCK Projects vs Spec Projects
|
On 2018-09-05 6:17 PM, Bill Shannon wrote:
In a previous discussion, perhaps in the Steering Committee,
I believe we came to the conclusion that the TCK needed to be
in a separate project from the spec. I think this was due to
some IP or licensing issue, perhaps because Spec Projects would
operate under different IP rules that we didn't want to apply to
code projects such as the TCK.
Does anyone remember the exact rationale for this required
separation between TCK Projects and Spec Projects?
Bill,
Wayne and I discussed this very topic yesterday.
Given that the TCK is a 1:1 with the Specification and the API, and that
all three artifacts need to be released at the same time, we're thinking
that they should all be managed as one project.
Our single reservation is that AIUI the people who work on the TCK and
the people who work on the spec document are often different. Is that
actually correct? We typically have a single committer list for everyone
involved in all aspects of a single project. If we need to manage
separate lists of committers between the spec doc/API/TCK that may drive
us towards a different solution.
Thoughts? Comments?
--
Mike Milinkovich
mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx
(m) +1.613.220.3223
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
