SVN

From Lanius CMS Wiki

Contents

Subversion (SVN)

SVN (Subversion) is a tool used by many software developers to manage changes within their source code tree; it is an open source version control system. It allows users to keep track of changes made over time to any type of electronic data; typical uses are versioning source code, web pages or design documents. Read more at Subversion article.

You can browse the current SVN tree using the following addresses:

Repository structure

This is the topmost outline of our current SVN repository:

  • core - master Lanius CMS source code
  • addons - all addon packages grouped by type
  • tools - sparse tools and utilities
  • drafts - source code drafts for future versions

Sub-structure

The core and addons directories contain three subdirectories:

  • trunk - the current under development source code
  • tags - previously released versions of the software package
  • branches - other development versions, alternative to trunk

Client software

How to checkout

Create a new directory (for example c:/inetpub/wwwroot under Windows), right click and perform a checkout from the following URL 

 https://laniuscms.svn.sourceforge.net/svnroot/laniuscms/core/trunk/

If you are using a unix/linux system the command line syntax is 

 svn co https://laniuscms.svn.sourceforge.net/svnroot/laniuscms/core/trunk/ laniuscms

If you do not want to checkout the Lanius CMS source code but some other package instead, change the last part accordingly.

Example: 

 https://laniuscms.svn.sourceforge.net/svnroot/laniuscms/addons/languages/it/

Logging in

You will not need any login credentials to login to our public SourceForge.net SVN repository.

Bug hunting

Use our issue tracker for your bug reports and your patches; but always be sure that you are working with the latest SVN revision!

See also Testing.

Developing

If you are going to actively contribute then ask to be given write permissions to the Lanius CMS repository in order to add your changes directly into the main trunk.

Commit rules

If you are using Subversion only to get the files, you will not need to read and understand the commit rules.

  1. Do not commit copyrighted material! Committed code and material must be compatible with the GPL version 2 license
  2. Always update before beginning your edit session
  3. Test your modifications before committing to the trunk
  4. Always commit when finishing your edit session
  5. Use descriptive log lines and start each line with an asterisk '*' (theoretically, for each edited file you should summarize the changes in functions' behaviours or user interface or fixes)
  6. Update also /core/trunk/version.php revision number if you have fixed a bug or implemented a feature

External Links

Retrieved from "http://wiki.laniuscms.org/index.php/SVN"
Personal tools
Create a book
  • Add wiki page
  • Collections help