I sometimes use GUI's on my development workstation. For Linux, the best I've found so far is a very old one named pysvn-workbench, which is sufficient for my needs. However, some of the documentation is lacking.
The configuration for pysvn-workbench is in ~/.WorkBench/WorkBench.xml. It contains some global preferences, then a list of all projects with their configurations. When preferences are changed, the file is renamed with a .old suffix, then recreated.
In that directory is also a log file for actions (WorkBench.log) and the most recently used log message (log_message.txt).
The WorkBench.log file appears to be rotated every 100k, ie it will rename the old log file to WorkBench.log.1, then start a new one.
Templates sound like a great idea, but figuring out how to set them up is pretty much undocumented. I finally started looking at the source and found the following:
Note I have not been able to figure out a way to set one template folder for all projects. You have to set the template folder for each one.
NOTE: one thing I want to try in the future is creating a fourth directory, stable. This will be a copy of the current stable version of the code. See below for more information.
As of Subversion 1.6, from a working copy, you can use the caret (^) as a substitute for the root URL of the project. Thus, if your you are in your working copy someplace, the following are equivilent. Note that even if you only checked out trunk, the tags are still accessible since it is the URL that is substituted for the caret. This can greatly reduce typing.
svn copy http://svn.example.com/project/trunk http://svn.example.com/project/tags/1.0 -m "Release 1.0"
cd /path/to/project svn copy ^/trunk ^/tags/1.0 -m "Release 1.0"
On the old machine
svnadmin dump --deltas reposname | bzip2 -c > /tmp/reposname.svn.dump.bz2
On the new machine
mkdir reposname svnadmin create reposname bunzip2 -c /tmp/resposname.svn.dump.bz2 | svnadmin load resposname
I've always been intrigued with people who use subversion with a tag that always points to the most recent stable version. Never figured out how they do it, but thanks to one of my associates, came up with this simple action when a new version has become your most recent stable version.
The following list of CLI commands will do this for you on any recent copy of subversion, assuming you are in the root of a checked out version of the project. In other words, in a cli go to your recently perfect, checked in version of your project, then run the following commands.
# get a list of all tags svn ls -v ^/tags # create a new tag for this version (ie, v3.5.1) svn copy ^/trunk ^/tags/v3.5.1 -m "Release v3.5.1" # delete tag stable svn delete ^/tags/stable -m "Changing latest stable version" # copy this version to stable tag svn copy ^/tags/v3.5.1 ^/tags/stable -m 'Setting v3.5.1 as stable' # list your tags again svn ls -v ^/tags
In the above, I'm using the caret (^) syntax to directly modify the subversion server. You can also do the same thing by explicitly using the URL. To find the URL, issue the command:
svn info | grep '^URL:' | cut -d':' -f2-
The URL listed after the colon can be used as a replacement for the caret above. Don't forget to remove 'trunk' from the end of that, however, since you are currently working in the trunk directory.
You can now publish your subversion address as http://svn.example.com/svn/project_name/tags/stable
If you wish, you could also simply create a new subdir on the same level as trunk and tags and do the same thing, I'm guessing (haven't tried it)