ProCKSI

= Subversion Policy =

When '''committing''' your code to the SVN repository, '''comment''' your action you are going to perform using the following '''abbreviations''':

||'''Abbreviation''' ||'''Type of Action''' ||'''Description'''
||b                  ||Bugfix               ||New code corrects a bug/defect
||e                  ||Enhancement          ||New code improves an existing feature
||f                  ||Feature              ||New code implements a new feature 
||a                  ||Administration       ||Perform an administrative task, e.g. renaming files/directories
||c                  ||Change               ||Perform a general change, which does not fall in any other category

Please refer to the TicketingPolicy on how to handle '''tickets''' correctly.
It describes how to '''reference''' and even '''close''' existing tickets while committing your code.

When '''committing''' publications (paper, posters, presentations, ...) to the repository, please refer to the [wiki:PublicationsPolicy Publications Policy] on how to '''lable''' them consistently.