The Eclipse Development Process has no notion of incubating
*components*.
In fact, the EDP has no formal notion of component; notions of
separate components within a mature project that are "incubating",
"interim", "experimental" or whatever are project-specific notions.
A project can consume any bits that have been *released* by another
project.
Permanent incubators, like the Nebula Incubator project cannot not
do releases.
So... if you're talking about a component that's from a release
version of mature projects Nebula or NatTable, then the EDP
considers you good-to-go.
If you're talking about a component from the Nebula Incubator, you
can't use it in another project's release until it's moved into the
parent project and included in a release.
For completeness, you can include released code from a project in
the incubation phase, but the consuming components would have to
conform to the incubation branding requirements.
Does this make sense?
Wayne
On 04/05/16 05:42 AM, Wim Jongman
wrote:
We are waiting on Wayne/EMO to respond.
Wayne/EMO:
* can release train projects consume incubation components
from Nebula?
* If so, is there a restriction on the version number that
these components must have e.g => 1.0.0?
--
Wayne Beaton on behalf of the Eclipse Management Organization
@waynebeaton
The Eclipse Foundation
|