5 ms·
I probably should have linked to the release notes instead, which are available here: http://subversion.apache.org/docs/release-notes/1.7.html http://subversio
by mmastrac 15y ago
I probably should have linked to the release notes instead, which are available here:
http://subversion.apache.org/docs/release-notes/1.7.html http://subversion.apache.org/docs/release-notes/1.7.html
Some big changes in 1.7 extracted from the release notes:
Working Copy Metadata Storage Improvements
A key feature of the changes introduced in Subversion 1.7 is the centralization of working copy metadata storage into a single location. Instead of a .svn directory in every directory in the working copy, Subversion 1.7 working copies have just one .svn directory—in the root of the working copy. This directory includes (among other things) an SQLite-backed database which contains all of the metadata Subversion needs for that working copy.
svn patch
Subversion 1.7 features a new subcommand called svn patch which can apply patch files in unidiff format (as produced by svn diff and other diff tools) to a working copy.
Improved HTTP protocol usage
Subversion 1.7 offers a simpler HTTP protocol variant that can be used when connecting to supported servers. This simpler protocol (sometimes referred to as HTTPv2) requires fewer client-server round trips to establish a connection, making Subversion much more performant on high-latency network connections.
- lucisferre 15y agoIs SVN just slowly evolving DVCS features? That seems to be the progression I've been noticing.
- mmastrac 15y agoIt appears so. This is good for SVN users - moving large codebases with years of commits, along with the associated build scripts and deployment data can be a big hassle. And that's before you factor in the effort required to move all of the users over. I wouldn't be surprised if we see 'offline' commits in SVN.
- dchest 15y agoNo. They decided to focus on being the best centralized version control system: http://lwn.net/Articles/381794/ http://lwn.net/Articles/381794/
- lucisferre 15y agoThat seems like a sensible vision for SVN, but it begs the question is there really still a need for centralized version control?
- udp 15y agoI'm not trolling here, this is a genuine question: What are the advantages of using SVN over Git? (assuming one was starting a new project and hadn't yet chosen a VCS)
- metajack 15y agoOne big one is that you can check out a working copy of a particular sub-path in the repository. This means you don't need the whole repo (or the repo's entire history) locally, which is necessary in workflows where build products and other giant binaries are stored in version control. I believe this is why many people still use Subversion and Perforce, etc.
- DannoHung 15y agoOf course, this is probably a not-so-great reason for doing so and reflects an inability to change build procedures/organizational workflows if this feature is absolutely vital.
- dchest 15y agoThis is actually a really cool feature. Basically, you can have one large repository to administer instead of lots of smaller ones, and you can treat any subdirectory level as a single repository. Want to checkout all Apache Software Foundation projects? svn checkout http://svn.apache.org/repos/asf/ Want to work on Apache httpd? svn checkout http://svn.apache.org/repos/asf/httpd/ Maybe you only care about mod_proxy? svn checkout http://svn.apache.org/repos/asf/httpd/httpd/trunk/modules/proxy/ Apache server becomes a subproject of the new Apache MegaOS? Just move /repos/asf/httpd/ to /repos/asf/megaos/httpd. See also FreeBSD repository: http://svnweb.freebsd.org/base/ http://svnweb.freebsd.org/base/
- dlsspy 15y ago> Want to checkout all Apache Software Foundation projects? > svn checkout http://svn.apache.org/repos/asf/ http://svn.apache.org/repos/asf/ Correction, that's all branches and all tags of all ASF projects. Not useful. > Want to work on Apache httpd? > svn checkout http://svn.apache.org/repos/asf/httpd/ http://svn.apache.org/repos/asf/httpd/ Again, all versions and all tags thereof. > Maybe you only care about mod_proxy? > svn checkout http://svn.apache.org/repos/asf/httpd/httpd/trunk/modules/proxy/ http://svn.apache.org/repos/asf/httpd/httpd/trunk/modules/pr... That's just the one version. Similarly, my project wants the latest sources under under specific branches from repositories from five different administrative domains. That's trivial in git. I can move them around freely, lock a revision of a particular repository while letting others move forward, have custom (potentially unpublished or unwelcome upstream) patches to fit into my build system or supported OSes that are tracked along with them. Subversion has externals for this same reason. It's no excuse for poor repository management.
- dchest 15y agoWhile switching to a single .svn directory seems good, there's also a feature lost: you can no longer move parts of your working trees around the filesystem without hassle.
- mey 15y agoThis is dangerous and error prone... What use case are you solving for by doing that?
- dchest 15y agoUse case... just moving stuff around. It was nice to have the freedom to treat any subdirectory as a separate working copy. Why is this dangerous? (note: I no longer use Subversion).
- mey 15y agoThe system wasn't designed with that consideration in mind, locking mechanisms can break when you do this and don't know that the folder is in use by another system (functionality varies per OS). If you are moving files to reorganize structure of a project, the .svn folders will cause conflicts, and you'll also loose the history of the move, (instead a continuous history of that structure, it'll appear as a new structure) Lastly, when supporting my developer pool with SVN, resolving corrupted .svn folders because of moving folders in correctly is a time consuming procedure and usually ends with an export command to kill all the .svn files, and risking blowing away changes in with a commit that ignores history.