Commit Process Policies
1 Overview
Before committing new code to the SVN repositories, one must first follow some simple rules that will ensure that the committed code will not break the build nor the basic features of the eXo Platform.
Following these following small rules will ensure a much better QA process and will improve the overall productivity of the development teams.
In short, it is not only the responsibility of the Test team to test the software but it is also the duty of each developer before committing.
2 Update before committing
Never commit without updating first!
Every commit should come with a message telling what you commit is about.
The comment should be concise and descriptive.
It should also reference an JIRA Issue key.
Here is an exemple :
ECM-2422 Update configuration to match JCR 1.9.x
In case a commit has a wrong comment, it is possible to alter it using the following command :
svn propset svn:log <message> -r<revision> --revprop <server>
5 Check the Continuous Build status
As soon as you have committed, tell the
Continuous build to build your project. If it fails, you probably have forgotten to add a file.
Newly submitted code should be java-commented. Documenting the code is key for adoption of eXo regarding customers and users. In addition, it allows newcomers to understand the product more quickly.
