|Re: [wtp-dev] The Bower IDE contribution|
TL;DR: Being in master != being in delivery for Mars.
On 03/23/2015 12:21 PM, Victor V. Rubezhny wrote:
That's not a problem: we can have code in master without shipping it on Mars, that's what I strongly believe is the best approach for easier collaboration, and to avoid risk of diverging branches.
Suggestion is that for a 1st integration in master, just include the bundles, not the pom files, do not update other pom files, feature.xml nor category.xml. So the code is there, people can work on it, but not altering the build and delivery.
Then next iteration would be to see if we can build it easily, include in the category.xml file as a separete entry, without modifying the "regular" JSDT feature so it wouldn't get in Mars. That would allow people who want to try it to get it from a p2 repository.
Being in master and being in Mars are totally separated topics, both technically and "organisationally". The most efficient and easier approach would be to have code in master right now, but not ship it in Mars. The fact that M6 is approaching doesn't forbid merging unrelated changes. It's actually something we could even add on the day before Mars if we wanted ;)
Back to the top