Subversion 1.7 is out
subversion.apache.org
Subversion 1.7 is out
1–10 of 41 posts
Re: Subversion 1.7 is out
#2I probably should have linked to the release notes instead, which are available here:
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.
Re: Subversion 1.7 is out
#3I probably should have linked to the release notes instead, which are available here: 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 di…
Is SVN just slowly evolving DVCS features? That seems to be the progression I've been noticing.
Re: Subversion 1.7 is out
#4yawn
Re: Subversion 1.7 is out
#5I probably should have linked to the release notes instead, which are available here: 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 di…
Is SVN just slowly evolving DVCS features? That seems to be the progression I've been noticing.
It 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.
Re: Subversion 1.7 is out
#6I probably should have linked to the release notes instead, which are available here: 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 di…
I'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)
Re: Subversion 1.7 is out
#7I probably should have linked to the release notes instead, which are available here: 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 di…
I'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)
One 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.
Re: Subversion 1.7 is out
#8I probably should have linked to the release notes instead, which are available here: 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 di…
I'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)
Setting up a SVN server takes seconds (infact it comes pre installed on all macs). Setting up a git server is a nightmare. If you have a small team like me (2-3 people max) then SVN easily meets all your needs.
Naturally Git will catch up and supersede but currently they are focusing on other stuff.
Re: Subversion 1.7 is out
#9Earlier quoted context omitted.
I'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)
One 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.
Of 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.
Re: Subversion 1.7 is out
#10I probably should have linked to the release notes instead, which are available here: 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 di…
I'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)
I use them both as well as Mercurial. My favorite is subversion, but that's only because I've been using it for years. The one thing I admire most about git is its branching. You can experiment very easily with crazy ideas and just throw away the branch if it doesn't work out. Learn them both and pick the one that works best for you. But you should be able to use any of them. From old-fashioned CVS (which is still widely used in industry) to git because as a professional programmer, you never know what your next employer or start-up buddy will be using. And really, they all share many things in common once you get past the new-fangled distributed features.
Edit: I should also mention that I prefer subversion's central repository approach and that I don't really need the distributed features of git but I can understand why Linus and kernel hackers do!