Skip to main content
Jump to: navigation, search

Difference between revisions of "Development Resources"

(Getting Answers: Add news groups link)
Line 1: Line 1:
=Reporting Bugs=
+
= Reporting Bugs =
  
 
* [https://bugs.eclipse.org/bugs/ Bug Reports]
 
* [https://bugs.eclipse.org/bugs/ Bug Reports]
Line 5: Line 5:
 
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.
 
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=
+
= Getting Answers =
  
 
* [http://www.eclipse.org/mail/ Mailing Lists]
 
* [http://www.eclipse.org/mail/ Mailing Lists]
Line 16: Line 16:
 
Asking questions on the IRC channels can be a quick way to get your questions answered, if the right person is online.
 
Asking questions on the IRC channels can be a quick way to get your questions answered, if the right person is online.
  
=Getting Code=
+
= Getting Code =
  
 
* [http://download.eclipse.org/ Eclipse Platform downloads page]
 
* [http://download.eclipse.org/ Eclipse Platform downloads page]
Line 23: Line 23:
 
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.
 
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=
+
= Committing Code =
  
 
* [[Development Conventions and Guidelines]]
 
* [[Development Conventions and Guidelines]]

Revision as of 12:02, 12 June 2006

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.

News Groups are open to the whole community, and are open to a broader range of questions than mailing lists.

Asking questions on the IRC channels can be a quick way to get your questions answered, if the right person is online.

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 Code

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.

Back to the top