As required by the Eclipse Development Process, this document describes the 2011 Eclipse Roadmap.
There are three main sections to this document:
The Roadmap is intended to be an ongoing document which undergoes incremental iterations. This document is the sixth version of the Eclipse Roadmap, and is labeled as version 6.0. In order to preserve this document while the underlying information evolves, the pages have been frozen by copying them from their original project hosted locations.
The goal of the Roadmap is to provide the Eclipse ecosystem with guidance and visibility on the future directions of the Eclipse open source community. An important element in this visibility is that the Roadmap help the EMO and the Board of Directors in determining which projects will be accepted by Eclipse during the life of this revision of the Roadmap. In other words, new projects must be consistent with the Roadmap. This does not mean that every new project must be explicitly envisaged by the Roadmap. It does mean that new projects cannot be inconsistent with the stated directions of Eclipse. In particular, Eclipse expects that incubator projects created in the Technology PMC will cover areas not explicitly described in the Roadmap.
As defined on our website, the role of the Eclipse Foundation is:
Eclipse is an open source community, whose projects are focused on building an open development platform comprised of extensible frameworks, tools and runtimes for building, deploying and managing software across the lifecycle. The Eclipse Foundation is a not-for-profit, member supported corporation that hosts the Eclipse projects and helps cultivate both an open source community and an ecosystem of complementary products and services.
As defined in our Bylaws the Purposes of the Eclipse Foundation are:
The Eclipse technology is a vendor-neutral, open development platform supplying frameworks and exemplary, extensible tools (the "Eclipse Platform"). Eclipse Platform tools are exemplary in that they verify the utility of the Eclipse frameworks, illustrate the appropriate use of those frameworks, and support the development and maintenance of the Eclipse Platform itself; Eclipse Platform tools are extensible in that their functionality is accessible via documented programmatic interfaces. The purpose of Eclipse Foundation Inc., (the "Eclipse Foundation"), is to advance the creation, evolution, promotion, and support of the Eclipse Platform and to cultivate both an open source community and an ecosystem of complementary products, capabilities, and services.
The following are the strategic goals of the Eclipse Foundation.
The goal of the Roadmap is to provide the Eclipse ecosystem with guidance and visibility on the future directions of the Eclipse open source community, and to involve the Eclipse membership in a dialog about those future directions. In that vein, this section discusses our current vision of the future as a set of future projects that expand the value of the ecosystem for all of its members.
The Themes and Priorities document prepared by the Requirements Council describes a number of requirements and focus areas for the existing Eclipse projects.
In addition to the Themes and Priorities requirements on existing projects in Helios, we envision future growth in Eclipse projects in the following major areas. These are areas in which we envision further growth in 2011-2012, and Eclipse-quality standards-based frameworks and tooling in these areas begin to become a reality.
2011 will see another release of the Eclipse 4 stream, Eclipse 4.1. The major goals of this new release include:
The progress of Eclipse 4 has been very positive and in June, 2012 it may be the major version of Eclipse used in the distros hosted at the Eclipse downloads page.
Orion launched in early 2011 and continue to receive emphasis and promotion throughout the year. Orion is not targeted at the classic Eclipse Developer, but is instead targeted at Web and RIA developers. This new development model and target audience will even futher diversify and grow our community in new and exciting directions.
The growing popularity of modeling and model-driven development has been an important driver for Eclipse projects for some time. We expect the momentum to grow even stronger in 2011. Eclipse-based modeling technologies such as Papyrus and Sphinx have become increasingly important for dealing with large, complex systems engineering and safety-critical systems. The Xtext project for supporting Domain Specific Languages has also generated enormous interest.
The Indigo release train in 2011 will see for the first time an EclipseRT Package available, and we expect EclipseRT will continue to grow and evolve. The Gemini and Virgo projects at Eclipse continue to demonstrate the community is starting to associate Eclipse as a great place to do runtimes. The key uniter of the various runtime technologies at Eclipse continues to be the Equinox implementation of the OSGi standard.
Projects such as Amazons AWS tooling and the Beanstalk product built on the Eclipse Platform give instant credibility to Eclipse as a important piece of the strategy for cloud tool providers. Eclipse has a role to play in the entire development lifecycle from development, deployment to testing and QA. In addition to tools, OSGi and Equinox will play an important role in the cloud. The ability to maintain configurations and deployments in large scale applications will be essential to scaling the cloud.
The process of creating the Eclipse Roadmap is described in the Eclipse Development Process. The key pieces are:
Back to the top