Skip to main content
Jump to: navigation, search

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

< CBI
(Cut-over)
Line 7: Line 7:
 
===Key Issues===
 
===Key Issues===
  
Some of the key issues we're working on include:
+
Please see the minutes of our [http://wiki.eclipse.org/CBI/November15_2012 November 15, 2012 discussion].
 
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=367581 Bug 367581] - do not generate new version qualifier unless there are actual code changes [DONE]
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=372794 Bug 372794] - CBI build of platform native SWT code [DONE]
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=370704 Bug 370704] - equinox launchers build [DONE]
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=369002 Bug 369002] - Isolate CBI platform build from uncontrolled software sources
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=369798 Bug 369798] - Add signing capability to the CBI build for the eclipse platform [DONE]
+
 
+
Please see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=372792 Bug 372792 - Status of CBI build for Eclipse Platform] for an aggregate of the status of all known issues.
+
 
+
 
+
  
 
==Code sprint #1==
 
==Code sprint #1==
Line 26: Line 16:
  
 
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.
 
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==
 
==Cut-over==
Line 31: Line 22:
 
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.
 
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 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].
 
+
  
 
The CBI built platform will use the same qualifiers that the PDE build used in order ensure the change is transparent as possible.
 
The CBI built platform will use the same qualifiers that the PDE build used in order ensure the change is transparent as possible.

Revision as of 11:19, 16 November 2012

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.

Back to the top