SVN / commits

New committers need to sign an agreement which hands over copyright to Geosparc.

All SVN commits should include the JIRA issue number at the start of the commit message, and a short description of the work done. The only times JIRA issue number are not needed is for making "obvious" changes like fixing typos.

Commits should be grouped by issue as much as possible/sensible (better two commits than one commit for fixing two issues, better one commit of five files than five commits of one file (for one issue)).

Development of the "latest-and-greatest" version happens in "trunk".

Continued development on earlier versions (when not "latest-and-greatest") occur in branches with the future version number as name.

When a release is cut, a tag with the release version as name is created. The release should be built from the tagged files.

After each commit, the system should still compile and all test-cases should still succeed. This is done through a continuous integration engine (Hudson)