What's New in TortoiseSVN 1.5

• Merge Tracking
• Sparse checkouts
• Cyrus SASL support for svnserve
• Changelist support
• Log message caching
• Repository browser
• Revision graph
• Client side hook scripts
• TortoiseMerge

WARNING: if a Subversion 1.5 client encounters a pre-1.5 working copy, it will automatically upgrade the working copy format as soon as it touches it, making it unreadable by older Subversion clients. If you are using several versions of Subversion on your machine, you need to be careful about which version you use in which working copy, to avoid accidentally upgrading the working copy format. This "auto upgrade" feature, however, does not occur with the new repository format.

Download TortoiseSVN 1.5

For more information

 What's New in Subversion 1.5

• Merge tracking (foundational)
• Sparse checkouts (via new --depth option)
• Interactive conflict resolution
• Changelist support
• Relative URLs, peg revisions in svn:externals
• Cyrus SASL support for ra_svn and svnserve
• Improved support for large deployments on FSFS, via sharding
• Improved FSFS optimizability, via immutable file isolation
• WebDAV transparent write-through proxy
• Improvements to copy and move
• Speed improvements, cancellation response improvements
• Easier to try experimental ra_serf DAV access module
• API changes, improvements, and much language bindings work
• More than 150 new bug fixes, enhancements

 

 Working Copy and Repository Format Changes

The working copy format has been upgraded. This means that 1.4 and older Subversion clients will not be able to work with working copies produced by Subversion 1.5. Working copies are upgraded automatically.

Similarly, the repository format has changed, meaning that 1.4 and older versions of Subversion tools that normally access a repository directly (e.g. svnserve, mod_dav_svn, svnadmin) won't be able to read a repository created by Subversion 1.5. But, repositories are not upgraded automatically.
Working Copy Upgrades

WARNING: if a Subversion 1.5 client encounters a pre-1.5 working copy, it will automatically upgrade the working copy format as soon as it touches it, making it unreadable by older Subversion clients. If you are using several versions of Subversion on your machine, be careful about which version you use in which working copy, to avoid accidentally upgrading a working copy. (But note that this "auto upgrade" behavior does not occur with the repositories, only working copies.)

If you accidentally upgrade a 1.4 working copy to 1.5, and wish to downgrade back to 1.4, use the change-svn-wc-format.py script. See this FAQ entry for details, and run the script with the --help option for usage instructions.
Repository Upgrades

The Subversion 1.5 server works with 1.4 and older repositories, and it will not upgrade such repositories to 1.5 unless specifically requested to via the svnadmin upgrade command. This means that some of the new 1.5 features will not become available simply by upgrading your server: you will also have to upgrade your repositories. (We decided not to auto-upgrade repositories because we didn't want 1.5 to silently make repositories unusable by 1.4 — that step should be a conscious decision on the part of the repository admin.)

After running svnadmin upgrade, you may wish to also run the svn-populate-node-origins-index program on the repository. Subversion 1.5 maintains a node-origins index for each repository, and builds the index lazily as the information is needed. But for old repositories with lots of revisions, it's better to create the index in one step, using the aforementioned tool, than to have live queries be slower until the index has built itself. See issue #3024 for details.

Download Subversion 1.5

For detail information