Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "CBI/Eclipse Platform Build Roadmap"

< CBI
(→‎Shadow the PDE build)
 
(20 intermediate revisions by one other user not shown)
Line 1: Line 1:
−
===Shadow the PDE build===
+
It is our intent to help the Eclipse platform project move to use the CBI build in time for Juno. The following is the roadmap for this transition.
  
−
During the time period from Juno M4 and SR0, the CBI build of the Eclipse Platform will shadow the PDE build. This time will be used for testing and developing any necessary components necessary to ensure that the CBI built Eclipse platform load is the same as the PDE built one with reasonable confidence.
+
==Shadow the PDE build==
  
−
[https://bugs.eclipse.org/bugs/show_bug.cgi?id=372792 Bug 372792 - Status of CBI build for Eclipse Platform] will aggregate the status of all known issues.
+
During the time period from [http://wiki.eclipse.org/Juno/Simultaneous_Release_Plan Juno] M4 (Dec.16/2012) and SR0(Jun.27/2012), the CBI build of the Eclipse Platform will shadow the PDE build. This time will be used for testing and developing any necessary components necessary to ensure that the CBI built Eclipse platform load is the same as the PDE built one with reasonable confidence.
  
−
===Cut-over===
+
===Key Issues===
  
−
Release candidates for Juno SR1 will be based on the CBI-built Eclipse platform with the intent of SR1 being released based on the CBI-built platform. The CBI built platform will use the same qualifiers that the PDE build used in order ensure the change is transparent as possible.
+
Please see the minutes of our [http://wiki.eclipse.org/CBI/November15_2012 November 15, 2012 discussion].
  
−
===FAQ===
+
==Code sprint #1==
  
−
Question: What does the CBI build of the Eclipse platform do?
+
A code sprint will take place in [http://wiki.eclipse.org/CBI/Code_Sprint_April_11_2012 April 11 & 12, 2012].
  
−
Answer: The CBI build of the Eclipse platform is intended to produce the same output as the PDE build, and thus facilitate packaging without noticeable change. The noticeable difference the CBI build of the platform makes is ease of use to build the platform. For example, the prototype has consistently demonstrated that a newcomer without prior experience can build the Eclipse platform with under 30 minutes of effort.
+
==Code sprint #2==
  
 +
A second code sprint took place September 12th to 21st @ IBM's offices in Ottawa, Canada. This sprint focused on tasks needed for the Eclipse platform team to cut over to CBI.
  
−
Question: What is the link between CBI & LTS?
 
  
−
Answer: The Long Term Support program is aimed at enabling organizations to support and maintain Eclipse software far into the future, for decades if needed. Part of the program enables maintenance committers working on behalf of the company to fix issues. Ensuring a very easy to use, very easy to maintain, and portable build was essential to the program. The fact that a build with these attributes also provides much benefit to the community was another good reason to do CBI.
+
==Cut-over==
  
 +
Our goal was for a release candidates for Juno SR1 to be based on the CBI-built Eclipse platform with the intent of SR1 itself (Sept.28,2012) being released based on the CBI-built platform. This turned out to be infeasible due to vacations and competing priorities.
  
−
Question: Won't CBI be kept behind a firewall at Eclipse?
+
The new plan is for SR2 (Feb. 2013) to be based on the CBI-built platform. The plan for cutover was discussed at the [http://wiki.eclipse.org/CBI/November15_2012 November 15, 2012 meeting].
  
−
Answer: No, the work done for CBI will be public and available and projects will be encouraged to leverage them. In the future, there may be some enhanced tools and features based on CBI designed to make Long Term Support (LTS) easier/more efficient/more effective. These might be available to members of the LTS working group only and enable a business model which supports the Eclipse Foundation.
+
The CBI built platform will use the same qualifiers that the PDE build used in order ensure the change is transparent as possible.
  
  
−
Question: Will my project be forced to move to CBI?
+
[[Category:CBI| ]]
−
 
+
−
Answer: No, no one is forcing projects to use CBI. But if CBI develops the way we intend, you'll likely feel there's much good value to use it and decide to move to CBI on your own. Part of the benefit include the really easy to use & powerful build. Part of the benefit is that using CBI allows the Eclipse Foundation's release engineer to provide some assistance to ensure your project has a really good build. Another important part of the CBI initiative is a Continuous integration facility and build farm maintained by the Eclipse Foundation... so you don't need to create & maintain one yourself somewhere else.
+
−
 
+
−
 
+
−
Question: Isn't this just-another-build system at Eclipse?
+
−
 
+
−
Answer: In truth, many of the technologies involved with CBI such as Maven, Tycho, Hydson, Git, etc. were already in use by a number of projects and being considered by others. Thus in a way, CBI is an evolutionary effort building on momentum in the community. Technologies such as Maven and Nexus (the artefact storage repository often used with Maven) are ubiquitous and very popular.
+

Latest revision as of 09:17, 10 May 2017

It is our intent to help the Eclipse platform project move to use the CBI build in time for Juno. The following is the roadmap for this transition.

Shadow the PDE build

During the time period from Juno M4 (Dec.16/2012) and SR0(Jun.27/2012), the CBI build of the Eclipse Platform will shadow the PDE build. This time will be used for testing and developing any necessary components necessary to ensure that the CBI built Eclipse platform load is the same as the PDE built one with reasonable confidence.

Key Issues

Please see the minutes of our November 15, 2012 discussion.

Code sprint #1

A code sprint will take place in April 11 & 12, 2012.

Code sprint #2

A second code sprint took place September 12th to 21st @ IBM's offices in Ottawa, Canada. This sprint focused on tasks needed for the Eclipse platform team to cut over to CBI.


Cut-over

Our goal was for a release candidates for Juno SR1 to be based on the CBI-built Eclipse platform with the intent of SR1 itself (Sept.28,2012) being released based on the CBI-built platform. This turned out to be infeasible due to vacations and competing priorities.

The new plan is for SR2 (Feb. 2013) to be based on the CBI-built platform. The plan for cutover was discussed at the November 15, 2012 meeting.

The CBI built platform will use the same qualifiers that the PDE build used in order ensure the change is transparent as possible.

Retrieved from "https://wiki.eclipse.org/index.php?title=CBI/Eclipse_Platform_Build_Roadmap&oldid=416478"

This page was last modified 09:17, 10 May 2017 by Frederic Gurr. Based on work by Andrew Ross.

Back to the top