SubversionServer

LIBISIS source code isheld in a subversion repository. The repository is world readable and though you can browse the LIBISIS library repository directly, but a better looking interface is provided by the ViewVC or TRAC browsers.

• Browse LIBISIS repository using ViewVC or TRAC

The repository can alse be interrogated for recent updates via a query form e.g show me all Library changes in the last month.

If you wish to receive an email when a change is made to the repository you should join the appropriate Mailing Lists. Alternatively, you can use an RSS feed to keep an eye on changes - TRAC supports this on pages with an orange "XML RSS Feed" icon at their foot such as:

• The Timeline pages for library
• The Revision Log pages for library

Login

To update files in these repositories you will need to use a program such as TortoiseSVN and also provide your LIBISIS Wiki username and password. Note that for subversion write access:

• If you Wiki username contains a space, write it with a space (i.e. do not replace the space with an _ as is done in WIKI URLs)
• You cannot use a "temporary password" (i.e. one that was emailed to you in response to a request). You must first log into MediaWiki with the temporary password and then go to account Special:Preferences and change the password.
• Your Wiki account must have an email address assocoiated with it and this address must have been validated. To provide and/or validate your email address, log in and go to your account Special:Preferences section.

Other information you will need to give to access are:

• URL of the subversion repository: https://svn.libisis.org/code/trunk

svn co --username "My WIKI Username" https://svn.libisis.org/code/trunk libisis

Please report any problems via out the IssueReporting system

Committing Changes

As well as needing a valid account, you will not be able to check-in changes unless you indicate (in the log message attached to the commit) which current issues on the IssueReporting system the changes either fix or refer to. This is done by enclosing special phrases in the commit message of the form:

command #1
command #1, #2
command #1 & #2 
command #1 and #2

where command is one of the commands detailed below and #1 means "issue number 1" on the system etc. You can have more then one command in a message. The following commands are supported and there is more then one spelling for each command (to make this as user-friendly as possible)

• closes, fixes
  The specified issue numbers are closed with the contents of this commit message being added to it.
• references, refs, addresses, re
  The specified issue numbers are left in their current status, but the contents of this commit message are added to their notes.

For example the commit message

    Changed blah and foo to do this or that. Fixes #10 and #12, and refs #12.

This will close issues #10 and #12, and add a note to #12 on the IssueReporting system. For a list of current issues see:

• Active tickets for the LIBISIS library