Svn practices

This page is still in draft. This line will be removed after the page been reviewed.

This page gathered svn practices frequently used by contributors and committers. If you have any advice to this page, please feel free to update it or discuss your idea in ooo-dev mail list.

Read-only access

Grab the whole source code

Grab a branche

Update your tree

Update to a specific revision

Check changes in specific revision

Write access

Commit your changes

Check changes before commit

Specify in the command line a list of the files/dirs that are changed to avoid accidentally committing unwanted changes.

Template for the log files should be used

svn commit ci -F ../mychangelog.txt change1 change2

Do not use 'svn commit -m "Your comment".

Update bugzilla with revision information for crossreference when you are done with the commit

How to create a branche of your own. When it comes to big or complicated changes, you may don't want to commit in stable branch directly.

How to merge your changes

For reference, FreeBSD has a SVN Primer, and the Merging section has some complete

Reference

A guide for new committers: http://www.apache.org/dev/new-committers-guide.html

Merge Instruction from FreeBSD: http://wiki.freebsd.org/SubversionPrimer/Merging