JAPI Subversion Developer Access
Checking out a normal working copy
To checkout a normal working copy of the latest development, checkout the trunk. This is what's called HEAD or MAIN/LATEST in other version control systems.
svn co https://svn.sourceforge.net/svnroot/japi japi/trunk
Current rules are this:
All files need a mime type.
For normal source code, use
svn propset svn:mime-type text/plain filenameto set the mime type.
All files with a text based mime type need a line ending setting.
JAPI convention is to always use
svn propset svn:eol-style LF filenameto set the line ending style.
Releases are created in the following way:
A branch with the new release name is created.
Usually the branch will increase the minor revision and use it as its name.
svn copy trunk branch/0.8. The policy for branches is that they aren't completely frozen, but only changes required for release and bug fixing are allowed.
- The branch is braught into releasable state. This usually should be zero effort, yet consider this a separate step.
The release is published.
As a part of the release publishing, a tag with the new release name and patch level is created.
svn copy branch/0.8 tag/0.8.0. The policy for tags is that they are completely frozen, tags must never ever be changed.
Checking out a released version
To checkout a released version, use
svn co https://svn.sourceforge.net/svnroot/japi japi/tag/version with
version being the release name.
To checkout, for example, version 0.8.0, use svn co https://svn.sourceforge.net/svnroot/japi japi/tag/0.8.0.