[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [eclipse-pmc] Clarifications about CBI, CBI-built Eclipse Platform, LTS
- From: Andrew Ross <andrew.ross@xxxxxxxxxxx>
- Date: Wed, 07 Mar 2012 21:16:18 -0500
- Delivered-to: email@example.com
- Organization: Eclipse Foundation
- Resent-date: Tue, 13 Mar 2012 08:27:52 -0400
- Resent-from: Andrew Overholt <overholt@xxxxxxxxxx>
- Resent-message-id: <20120313122752.GA2658@redhat.com>
- Resent-to: eclipse-pmc@xxxxxxxxxxx
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120209 Thunderbird/10.0.1
Hi Andrew, Everyone
Thank you for the interest and support for CBI & LTS.
On 03/07/2012 04:11 PM, Andrew Overholt wrote:
That's right, and broader than a tycho template. The CBI initiative is
aimed at making building easier for all Eclipse projects. CBI involves a
collection of technologies such as Maven, Tycho, Hudson, Git, and so
forth - many of these are being used today so this is an evolutionary
We were briefly discussing $subj on the PMC call today and I'm hoping
you can clarify some items for us:
1. CBI itself is intended to be a Tycho template or something that can
be used by all Eclipse projects, right? Can you give any more
Enabling the LTS program is an important catalyst for CBI.
There's a service aspect of CBI for which we hired a release engineer
and contracted to leverage some of Igor's time. This is also where
examples and guidance come in to help projects benefit from this work.
That's right. Much of the work thus far has been aimed at the Eclipse
platform build prototype. While much work remains, the prototype
currently enables building the Eclipse platform with just a few commands
and minimal set up. The work we're doing in CBI evolutionary responding
to the new requirements presented by LTS and hopefully providing some
added goodness & ease of use to the community along the way.
2. Is the first target for the CBI the Eclipse Platform? It is my
understanding that EPP packages pull from the simultaneous repo so
does this mean that the CBI-built Platform will be in the
simultaneous repo alongside the Platform contributed by the Eclipse
project? If so, I can only assume that qualifiers will be different
which I guess is a good thing so bug reports can be routed to the
We're figuring the packaging part out right now. There are concerns
about the risks/costs of two versions of the Eclipse platform floating
around. There's not much we can do to change where we are in terms of
time/the release schedule. If we can avoid multiple versions by some
appropriate means which still enables LTS, then that would be a good thing.
Yes, we're aiming for the CBI-built version of the Eclipse platform to
be fed into the first release to enter LTS, Juno.
3. AIUI, the Platform from Juno (I guess the CBI-built version?) will
form the basis of the first LTS release. If this is the case, will
the Platform alone be supported for "the long term"?
The LTS industry working group Steering Committee will decide which
projects are included into LTS. For now, since the SC isn't yet formed,
we're assuming a pragmatic selection of Simultaneous release projects.
Thanks for the clarifications and sorry if this information is collected
somewhere else and I just missed it :)
Thank you for asking. I don't think we can over communicate about these