Eclipse Project Development

Releases currently under development

Eclipse Platform Project 3.4 Plan
This document lays out the feature and API set for the 3.4 release of Eclipse.
Eclipse Project 3.4 Endgame Plan
Information about we plan to wrap up the 3.4 (Ganymede) release of Eclipse.
Release Engineering Build Schedule
Schedule for Eclipse Platform nightly, integration, and milestone builds.

Development Process

Conventions and Guidelines
Look here for the for the coding standards, naming conventions, and other guidelines we use to help ensure eclipse presents to users and developers as a unified whole rather than as a loose collection of parts.
Bug Reports
Eclipse uses Bugzilla as our bug tracking system. Bugzilla has a wide following within the open source community and directly supports the workflows associated with distributed development (e.g., email notification). You can sign up for your own Eclipse bugzilla ID and start contributing bug reports.
CVS Repository
We use the Concurrent Versioning System (CVS) to support concurrent distributed development, and we use Eclipse as our CVS client because it supports CVS directly.. All Eclipse development is carried out in this repository. The server supports both "extssh" and "pserver" type CVS connections - "pserver" only works for anonymous access.
Mailing Lists
Eclipse uses mailing lists for development coordination, design discussions, voting, announcements etc.
Eclipse Committers
List of Eclipse Project committers.

API Resources

How to use the Eclipse API
Guidelines for using Eclipse APIs to ensure that your code will keep working as Eclipse evolves.
Evolving Java-based APIs
Guidelines for how to evolve Java-based APIs while maintaining compatibility with existing client code.
Eclipse APIs: Line in the Sand (pdf)
The philosophy, psychology, and sociology of APIs, EclipseCON 2004 presentation by Jim des Rivieres
API First (pdf)
Best practices for API development based, EclipseCON 2005 presentation by Jim des Rivieres
Eclipse Performance
Poor performance is a bug and should be tested for, tracked and fixed in the same way. The Eclipse Performance page is a collection of resources and information aimed at helping plug-in developers do just that.

Historical information about past releases

Eclipse Project 3.3.2 Endgame Plan
Information about we plan to wrap up the 3.3.2 (Europa winter maintenance) release of Eclipse.
Eclipse Platform Project 3.3 Plan
This document lays out the feature and API set for the 3.3 release of Eclipse.
Eclipse Project 3.3.1 Endgame Plan
Information about we wrapped up the 3.3.1 (Europa fall maintenance) release of Eclipse.
Eclipse 3.3 Endgame Plan
Information about we wrapped up the 3.3 (Europa) release of Eclipse.
Eclipse Project 3.2.2 Endgame Plan
Information about we wrapped up the 3.2.2 (Callisto winter maintenance) release of Eclipse.
Eclipse Project Bugs Counts
Information on outstanding bugs in the Eclipse project main development stream.
Eclipse Project 3.2 Endgame Plan
Information about how we wrapped up the 3.2 (Callisto) release of Eclipse.
Eclipse Platform Project 3.2 Plan
This document lays out the feature and API set for the 3.2 release of Eclipse.
Eclipse 3.1 Maintenance Release Schedule
Timeline for 3.1.x maintenance stream.
Eclipse Project Bugs Counts
Information on outstanding bugs in the Eclipse project main development stream.
Eclipse 3.1 by the numbers
Some light-hearted statistics for the 3.1 release cycle.
Eclipse Project 3.1.2 Endgame Plan
Information about how we wrapped up the 3.1.2 maintenance release of Eclipse.
Eclipse Project 3.1.1 Endgame Plan
Information about how we wrapped up the 3.1.1 maintenance release of Eclipse.
Eclipse Project 3.1 Plan (Final)
This document lays out the feature and API set for the 3.1 release of Eclipse.
Eclipse Platform 3.1 Release Review (pdf)
Presentation to Eclipse Foundation prior to shipping the 3.1 release.
Eclipse 3.1 Proposals
Links to proposals and working documents for various 3.1 plan items.
Eclipse Project 3.1 Endgame Plan
Information about how we wrapped up the 3.1 release of Eclipse.
Eclipse 3.0 Maintenance Release Schedule
Timeline for 3.0.x maintenance stream (nothing further planned).
Eclipse Project 3.0.2 Endgame Plan
Information about how we wrapped up the 3.0.2 maintenance release of Eclipse.
Eclipse Project 3.0.1 Endgame Plan
Information about how we wrapped up the 3.0.1 maintenance release of Eclipse.
Eclipse Project 3.0 Plan (Final)
This document lays out the feature and API set for the 3.0 release of Eclipse.
Eclipse 3.0 by the numbers
Some light-hearted statistics for the 3.0 release cycle, compiled by John Arthorne.
Eclipse 3.0 Endgame Plan
Information about how we wrapped up the 3.0 release of Eclipse.
Eclipse 3.0 Porting Guide
Up-to-the-moment advise for porting existing plug-ins to Eclipse 3.0.
Eclipse 3.0 Proposals
Links to proposals and working documents for various 3.0 plan items.
Eclipse 3.0 Component Milestone Plans
Details about what each of the component teams is working on for the upcoming milestone.
Eclipse 3.0 API Status
Status of Eclipse API packages and extension points in 3.0 development stream.
The Next Eclipse
Early discussion about what the 3.0 release of Eclipse should be.
Eclipse Project 2.1 Plan (Final)
This document lays out the feature and API set for the 2.1 release of Eclipse.
Eclipse 2.1 Maintenance Release Schedule
Timeline for 2.1.x maintenance stream (nothing further planned).
Eclipse 2.1 Endgame Plan
Information about how we wrapped up the 2.1 release of Eclipse.
Eclipse 2.1 Milestone Plans
Links to the 2.1 milestone plans for each Eclipse team (subproject).
Eclipse 2.1.1 Endgame Plan
Information about how we wrapped up the 2.1.1 maintenance release of Eclipse.
Eclipse 2.1.2 Endgame Plan
Information about how we wrapped up the 2.1.2 maintenance release of Eclipse.
Eclipse 2.1.3 Endgame Plan
Information about how we wrapped up the 2.1.3 maintenance release of Eclipse.
Top "Ten" Issues List
This document describes the key issues that we are working on for 2.1 and additional issues we will likely be working on soon.
Eclipse 2.0 Retrospective Actions
In August 2002 retrospective sessions were held with the various component teams to discuss what worked (and didn't work) with the 2.0 release. Based on the feedback collected during these sessions, we agreed on actions for the 2.1 effort.