Scala Code Management and Bug Reporting

We strive to make the Scala software always better, and to iron out all defects and bugs that might show up from time to time. In order to track bug reports and patch submissions, we make use of the following tools:

• The Scala Trac
  This is quite simply the resource to keep track of Scala issues and bugs, and their resolution. The system is based on the very popular Trac software, and all of us Scala developers make continuous use of it. The Trac website also implements our online SVN repository browser, and a few webpages related to Scala bug tracking. Everyone is welcome to open an account on our Trac system, and contribute to the improvement of the Scala software by filing tickets. If already have an account on scala-lang.org and would like to create a trac account, we suggest you to use the same username and email address on both, as the account systems of the two websites might be integrated in the future.
   
• Scala Jenkins
  We use the Jenkins continuous integration system to support Scala development. Every time we commit something to the Scala repository, a check-in test is automatically performed, and will warn us if anything broke. Additionally, every night a larger suite of tests is automatically performed. You can verify the current status of present and past tests on the Scala Jenkins server.
   
• Code Review
  We strive to have our code changes reviewed by others, as a form of quality control. If a developer submits a patch that does anything more than a trivial change, for instance if the patch changes a library functionality, or adds a new compiler option, or does anything else that may possibly have unintended effects, the code gets also submitted to our Code Review tool for approval. This resource is mainly used by the Scala Core Team, but it is available to all the public.