IntroductionEclipse has advanced quite quickly with new use-cases (RCP, Equinox, server side, etc.) and new technologies. However, to date Update Manager has not been enhanced to support or exploit these changes thus limiting the applications being developed. Even though the 3.3 plan has items to overcome these limitations, no new work has been done due to time and resource constraints. In order to ensure Update Manager receives appropriate attention in the next release of Eclipse, we are proposing the creation of a provisioning work area to develop new technologies and explore existing ones. The goal is for this work to graduate to be a replacement for Update Manager.
Scope of the proposalIn order to increase our chance of success, the scope of this incubator will be limited to the creation of a client-side provisioning framework that is functionally equivalent to the current Update Manager yet is more flexible and extensible. The key characteristics researched by this work are:
CommunityTo ensure the suitability of the solution to a wide set of use cases, we are actively looking for interested parties (with or without technology) with definite interest in this area who are willing to contribute time and resources.
TimelineGiven the foreseen impact of this work, we will have to operate under an aggressive schedule to be able to quickly produce a stable result. This will allow the platform team and interested parties ample time to review and buy in to this new provisioning story before integration into the Eclipse platform. If accepted, we intend to start integration of the new provisioning story as early as September 2007 and reach completion in December 2007, thus leaving us the rest of the release cycle for polish.
ResourcesPlease direct comments or questions to email@example.com.