|[cross-project-issues-dev] Re: CQs, Orbit, PMCs and Galileo - Clarification|
Martin pointed out a slight but key wording mistake. The second
paragraph should read|
So, if you are part of the train and are entering CQs for *reuse of* third party code and
that code is not coming from Orbit, you are not complying with the release plan.
The IP process defines "reuse" in this context as using in your Eclipse project a third party lib that has been approved for use in another Eclipse project. Initial inclusions of third party code should be requested against the original consuming project. Ideally that project team would proactively seek to put the library into Orbit by entering a second CQ and doing the bundling work in Orbit rather than their project. If they don't and you want to use the same library, someone needs to do the (minimal) work to get it in Orbit.
The basic premise here is that third party code being included in Galileo should be coming through Orbit. That is the purpose of Orbit. We all win by using Orbit. It eliminates duplicate work, duplicate code, subtle errors and differences as well as providing a valuable resource for the Eclipse community at large.
Jeff McAffer wrote:
As I understand the Galileo release plan,
Back to the top