|
On 03/25/2015 05:41 PM, Mickael Istria
wrote:
On 03/25/2015 03:34 PM, Konstantin
Komissarchik wrote:
1.
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.
You're right, in that case, we should talk about "Experimental"
plugins (Bower) for a mature project (JSDT)
Correct
2.
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.
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.
All the dependencies are existing Eclipse project (JGit is the main
one). The code itself (initial one) has passed the IP approval:
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=9173
But as we're still modifying it, it looks like we have to get
another approval on it before merging it into a release stream.
3.
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 p2 repositories.
As far as I know, there is no plan to release Bower integration
separately from JSDT. @Victor: is there?
I don't have such plans.
/Victor
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev
|
