For a Technical Specification, constituent artifacts include the Specification Documents, zero or more other Specifications, one or more Compatible Implementations licensed under an Open Source License, and exactly one associated TCK.
For a Technical Specification, constituent artifacts include the Specification Documents, zero or more other Specifications, one or more Compatible Implementations licensed under an Open Source License, and exactly one associated TCK.
.Conceptual structure of a Technical Specification
.Conceptual structure of a Technical Specification
When the result is a Major or Minor Release, a Project Team must engage in a xref:efsp-reviews-release[Release Review] to ratify a Specification Version as a Final Specification. When the result is a Service Release, a Specification Version is automatically a Final Specification.
When the result is a Major or Minor Release, a Project Team must engage in a xref:efsp-reviews-release[Release Review] to ratify a Specification Version as a Final Specification. When the result is a Service Release, a Specification Version is automatically a Final Specification.
...
@@ -366,7 +398,7 @@ No reviews are required for a Service Release.
...
@@ -366,7 +398,7 @@ No reviews are required for a Service Release.
To produce a <<efsp-versions,Specification Version>> (with the exception of <<efsp-releases-service, Service Releases>>) a Project Team must engage in a formal Release Cycle under the supervision of the PMC and the Specification Committee.
To produce a <<efsp-versions,Specification Version>> (with the exception of <<efsp-releases-service, Service Releases>>) a Project Team must engage in a formal Release Cycle under the supervision of the PMC and the Specification Committee.
[graphviz, images/lifecycle, svg]
[graphviz, images/efsp-lifecycle, svg]
.An overview of the Eclipse Foundation Specification Process
.An overview of the Eclipse Foundation Specification Process
----
----
include::diagrams/efsp_lifecycle.dot[]
include::diagrams/efsp_lifecycle.dot[]
...
@@ -444,8 +476,37 @@ The Specification Document for the Final Specification must be distributed as re
...
@@ -444,8 +476,37 @@ The Specification Document for the Final Specification must be distributed as re
A TCK for a Final Specification in composite must be distributed under the Eclipse Foundation Technology Compatibility Kit License. Other technical artifacts must be distributed under an Open Source License.
A TCK for a Final Specification in composite must be distributed under the Eclipse Foundation Technology Compatibility Kit License. Other technical artifacts must be distributed under an Open Source License.
.Conceptual model of the transition from a Specification Version to a Final Specification. Note that no specific packaging technology or structure should be implied from this diagram.
.Conceptual model of the transition from a Specification Version to a Final Specification.