Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[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

Jeff McAffer wrote:
As I understand the Galileo release plan[1],
    "Any new third-party plug-ins that are common between projects must be consumed
    via Orbit; the final Galileo release will not have duplicate third-party libraries"

So, if you are part of the train and are entering CQs for third party code and that code is not coming from Orbit, you are not complying with the release plan.

To save on effort for the IP team, PMCs should be careful when approving CQs for third party libs that are NOT coming from Orbit when being requested by projects on the train.  In particular, there should be no CQs marked Galileo (P1) that are for reuse from projects other than Orbit.

So, what do you do if you have entered or are about to enter one of these errant CQs? 
- First, look to see if the lib is already in Orbit
- If it is, make sure your CQ indicates the related Orbit CQ rather than one from a random other project
- If it is not, you need to get the lib into Orbit.  See the Orbit wiki pages[2] for more info on that
- Once you have someone who will put it in Orbit, they can enter the required CQ for adding it to Orbit.  Then you ensure that your CQs reference the Orbit CQ.
- Crack a frosty beverage

Jeff

[1] http://wiki.eclipse.org/Galileo
[2] http://wiki.eclipse.org/index.php/Orbit

Back to the top