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.
Development Resources
Reporting Bugs
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.
Getting Answers
Eclipse uses mailing lists for development coordination, design discussions, voting, announcements etc.
Asking questions on the IRC channels can be a quick way to get your questions answered.
Getting Code
Links to Nightly, Milestone and Maintenance builds, plus release notes, performance results, and other Platform goodies.
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.
Committing Patches
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.
Eclipse committers can use this interface to change their eclipse.org password, to run some stats or to get general information about the eclipse.org infrastructure.