On 03/25/2015 03:34 PM, Konstantin
You're right, in that case, we should talk about "Experimental"
plugins (Bower) for a mature project (JSDT)
The “incubating” term has special meaning per EDP. A mature
project cannot have incubating code in its source repository.
That doesn’t mean that you couldn’t use a different term…
alpha, beta, etc.
I assumed there were already IP approval for Bower, maybe I'm wrong.
If not, then I understand that it's currently a blocker for merging
in JSDT, and opening CQs should be top-priority.
If this code is merged into JSDT source repo, it and all of
its dependencies must be able to pass the IP review before
JSDT 3.7 can release. The IP review covers the entire source
repo, even if a certain piece isn’t being released.
As far as I know, there is no plan to release Bower integration
separately from JSDT. @Victor: is there?
Only a project can have releases. There is no formal notion
of a component and you cannot have informal components
making releases, so no Bower IDE 0.1 release, for instance.
That doesn’t mean that you couldn’t exclude some
functionality that’s in the source repo from a JSDT release
or deliver different pieces of a JSDT release in different