Browse LIMB respository on the web
If you don't want to check out the working copy you can alternatively simply browse the LIMB repository using Apache built-in viewer
If you want to have a complete repository tracking tool at your hands try Limb fisheye, a Java based repository "swiss-army knife".Anonymous SVN Access
The latest working copy of LIMB 2.x can be checked out through anonymous account with the following command.
svn co https://svn.limb-project.com/limb/2.x/trunk
Browse the repository tree before checking it out! If you don't want to checkout all branches and tags.
You shouldn't checkout the whole repository since it contains all dev.branches and tags. The current dev. branch of LIMB 2.x is located in the /limb/2.x/trunk, while LIMB 3.x has a bit more complicated repository layout since each package has its own development branch. In order to simplify the checkout procedure all trunk versions of LIMB 3.x packages are stored under 'limb' directory, e.g. /limb/3.x/limb/core
From time to time we fork branches from the trunk since they're very useful for trying some experimental features in isolation from the main development. These branches normally get merged back with the trunk eventually. LIMB 2.x experimental dev. branches are located at /limb/2.x/branches and for LIMB 3.x all experimental dev. branches are located in a separate 'branches' directory, e.g. /limb/3.x/branches/core-0.1.0.
Once an official release is made it's available as a tag in repository. All official releases(or tags) go to /limb/2.x/tags for LIMB 2.x and for LIMB 3.x they go to a separate 'tags' directory, e.g. /limb/3.x/tags/core-0.1.0.
Developer SVN write access via Web DAV
Only project developers have write access to the LIMB subversion repository using this method. Enter your login and password when prompted during the check-in procedure.
If you want to get SVN dev. account and take active part in LIMB development, contact us, via forum or dev. mailing list, please(you can also send your patches and bugfixes, we'll give you a proper credit in the CHANGELOG :) )
|
