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.
CBI/Eclipse Platform Build Roadmap
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
Some of the key issues we're working on include:
- Bug 367581 - do not generate new version qualifier unless there are actual code changes [DONE]
- Bug 372794 - CBI build of platform native SWT code [DONE]
- Bug 370704 - equinox launchers build [DONE]
- Bug 369002 - Isolate CBI platform build from uncontrolled software sources
- Bug 369798 - Add signing capability to the CBI build for the eclipse platform [DONE]
Please see Bug 372792 - Status of CBI build for Eclipse Platform for an aggregate of the status of all known issues.
Code sprint #1
A code sprint will take place in April 11 & 12, 2012.
Code sprint #2
A second code sprint will take place in July 2012 prior to cut-over.
Cut-over
Release candidates for Juno SR1 will 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. The CBI built platform will use the same qualifiers that the PDE build used in order ensure the change is transparent as possible.