Skip to main content
Jump to: navigation, search

Difference between revisions of "Development Resources"

(add cite to page about callisto bugs)
(Organize the contents a bit by topic)
Line 1: Line 1:
* [http://download.eclipse.org/ Eclipse Platform downloads page]
+
=Reporting Bugs=
Links to Nightly, Milestone and Maintenance builds, plus release notes, performance results, and other Platform goodies.
+
 
+
 
+
* [[Development 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.
+
+
  
 
* [https://bugs.eclipse.org/bugs/ Bug Reports]
 
* [https://bugs.eclipse.org/bugs/ Bug Reports]
 
* [[Field Guide to Callisto Bugs]]
 
* [[Field Guide to Callisto 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.
 
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.
 
  
* [http://dev.eclipse.org/viewcvs/ CVS Repository]
+
=Getting Answers=
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.
+
+
  
 
* [http://www.eclipse.org/mail/ Mailing Lists]
 
* [http://www.eclipse.org/mail/ Mailing Lists]
 
Eclipse uses mailing lists for development coordination, design discussions, voting, announcements etc.
 
Eclipse uses mailing lists for development coordination, design discussions, voting, announcements etc.
+
 
 +
* [[IRC]]
 +
Asking questions on the IRC channels can be a quick way to get your questions answered.
 +
 
 +
=Getting Code=
 +
 
 +
* [http://download.eclipse.org/ Eclipse Platform downloads page]
 +
Links to Nightly, Milestone and Maintenance builds, plus release notes, performance results, and other Platform goodies.
 +
* [http://dev.eclipse.org/viewcvs/ 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.
 +
 
 +
=Committing Patches=
 +
 
 +
* [[Development 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.
  
 
* [https://dev.eclipse.org/committers/ Committer tools]
 
* [https://dev.eclipse.org/committers/ Committer tools]
 
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.
 
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.
 
  
 
* [http://www.eclipse.org/legal/newcommitter.php Add a New Committer]
 
* [http://www.eclipse.org/legal/newcommitter.php Add a New Committer]

Revision as of 01:09, 9 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.

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.

Copyright © Eclipse Foundation, Inc. All Rights Reserved.