|Re: [wtp-dev] The Bower IDE contribution
I am refereeing to restrictions imposed by Eclipse Development Process (EDP) rather than technical issues. Note that I am not saying these issues are insurmountable, but I’ve seen enough red flags in this thread that I thought I should speak up. Keep the following in mind…
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.
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.
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.
Hope this helps.
On 03/24/2015 08:25 PM, Konstantin Komissarchik wrote:
It's easier for contributors, committers and adopters to have JSDT project owning its incubating part and then putting them in the WTP Incubator. However, once Bower IDE is included in JSDT build, it's easy for the WTP Incubator build to also list and include the Bower IDE features in the output p2 repo.
Keep in mind that if you are adding this to JSDT master and including it in the build, you are saying that this feature is part of WTP 3.7 release
That's not true. JSDT also has a dedicated site created by local builds, which is a separate delivery from WTP. If we add it only to that site, it doesn't provide it in WTP, and contributors/testers can install Bower IDE after having built it locally.
Back to the top