Code Changes Process

This page is for developers who want to contribute to the project.

One branch for one issue

Please create a branch for every new issue. Once you're done with the development and the testing, please create a pull request.

Commit format

Please use the format #<issue number>: <short change description>.

Example: #24: Fixed problem with method foobar(). The bar was missing.

Jenkins

There is a ustok Jenkins (see http://212.227.135.132:8080) we use for building, testing and releasing our tools. On the Jenkins, there should be a swtbotspy_build job which

1. builds the spy including running unit tests and
2. deploys the spy onto the dev updatesite location.

When doing the code review (that is, processing a pull request), the reviewer should also check that the changes are approved by Jenkins.