{"id":5016,"date":"2011-10-12T10:13:39","date_gmt":"2011-10-12T09:13:39","guid":{"rendered":"http:\/\/www.itwriting.com\/blog\/5016-subversion-1-7-released-just-one-svn-directory-per-working-copy.html"},"modified":"2011-10-12T10:13:39","modified_gmt":"2011-10-12T09:13:39","slug":"subversion-1-7-released-just-one-svn-directory-per-working-copy","status":"publish","type":"post","link":"https:\/\/www.itwriting.com\/blog\/5016-subversion-1-7-released-just-one-svn-directory-per-working-copy.html","title":{"rendered":"Subversion 1.7 released: just one .svn directory per working copy"},"content":{"rendered":"<p>Yesterday saw the 1.7 release of <a href=\"http:\/\/subversion.apache.org\/\" target=\"_blank\">Subversion<\/a>, the widely used open source version control system. It is a significant release with many new features, bug-fixes and performance improvements, and I suggest reading the <a href=\"http:\/\/subversion.apache.org\/docs\/release-notes\/1.7.html\" target=\"_blank\">release notes<\/a> or complete <a href=\"http:\/\/svn.apache.org\/repos\/asf\/subversion\/trunk\/CHANGES\" target=\"_blank\">change log<\/a>. One thing to highlight is that the default working copy metadata storage is now a single sqlite database per working copy, rather than a .svn direction containing metadata in sub-directory.<\/p>\n<p>I upgraded my <a href=\"http:\/\/tortoisesvn.tigris.org\/\" target=\"_blank\">TortoiseSVN<\/a>, which is already updated to 1.7, and tried upgrading one of my own projects. Here is the .svn folder before the upgrade:<\/p>\n<p><a href=\"http:\/\/www.itwriting.com\/blog\/wp-content\/uploads\/2011\/10\/image23.png\"><img loading=\"lazy\" decoding=\"async\" style=\"background-image: none; border-bottom: 0px; border-left: 0px; margin: 0px; padding-left: 0px; padding-right: 0px; display: inline; border-top: 0px; border-right: 0px; padding-top: 0px\" title=\"image\" border=\"0\" alt=\"image\" src=\"http:\/\/www.itwriting.com\/blog\/wp-content\/uploads\/2011\/10\/image_thumb23.png\" width=\"204\" height=\"216\" \/><\/a><\/p>\n<p>and after<\/p>\n<p><a href=\"http:\/\/www.itwriting.com\/blog\/wp-content\/uploads\/2011\/10\/image24.png\"><img loading=\"lazy\" decoding=\"async\" style=\"background-image: none; border-bottom: 0px; border-left: 0px; margin: 0px; padding-left: 0px; padding-right: 0px; display: inline; border-top: 0px; border-right: 0px; padding-top: 0px\" title=\"image\" border=\"0\" alt=\"image\" src=\"http:\/\/www.itwriting.com\/blog\/wp-content\/uploads\/2011\/10\/image_thumb24.png\" width=\"204\" height=\"182\" \/><\/a><\/p>\n<p>Those pesky .svn folders can be a nuisance so this is a welcome change, although there is a downside as the release notes warn:<\/p>\n<blockquote>\n<p>It is not safe to copy an SQLite file while it&#8217;s being accessed via the SQLite libraries. Consequently, duplicating a working copy (using <tt>tar<\/tt>, <tt>cp<\/tt>, or <tt>rsync<\/tt>) that is being accessed by a Subversion process is not supported for Subversion 1.7 working copies, and may cause the duplicate (new) working copy to be created corrupted.<\/p>\n<\/blockquote>\n<p>Subversion is less fashionable since the advent of distributed version control systems like <a href=\"http:\/\/git-scm.com\/\" target=\"_blank\">git<\/a> and <a href=\"http:\/\/mercurial.selenic.com\/\" target=\"_blank\">mercurial<\/a>; though for corporate development Subversion remains popular because a centralised system is easier to control.<\/p>\n<p>WANdisco\u2019s Jessica Thornsby has a <a href=\"http:\/\/blogs.wandisco.com\/2011\/10\/11\/top-new-features-in-subversion-1-7-wc-ng-pristines\/\" target=\"_blank\">helpful post<\/a> on the new 1.7 features more details on the benefits of the new working copy metadata managements system.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Yesterday saw the 1.7 release of Subversion, the widely used open source version control system. It is a significant release with many new features, bug-fixes and performance improvements, and I suggest reading the release notes or complete change log. One thing to highlight is that the default working copy metadata storage is now a single &hellip; <a href=\"https:\/\/www.itwriting.com\/blog\/5016-subversion-1-7-released-just-one-svn-directory-per-working-copy.html\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">Subversion 1.7 released: just one .svn directory per working copy<\/span> <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[62,67,79,80],"tags":[417,849,877,943],"class_list":["post-5016","post","type-post","status-publish","format-standard","hentry","category-open-source","category-professional","category-software","category-software-development","tag-git","tag-software-development","tag-subversion","tag-version-control"],"_links":{"self":[{"href":"https:\/\/www.itwriting.com\/blog\/wp-json\/wp\/v2\/posts\/5016","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.itwriting.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.itwriting.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.itwriting.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.itwriting.com\/blog\/wp-json\/wp\/v2\/comments?post=5016"}],"version-history":[{"count":0,"href":"https:\/\/www.itwriting.com\/blog\/wp-json\/wp\/v2\/posts\/5016\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.itwriting.com\/blog\/wp-json\/wp\/v2\/media?parent=5016"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.itwriting.com\/blog\/wp-json\/wp\/v2\/categories?post=5016"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.itwriting.com\/blog\/wp-json\/wp\/v2\/tags?post=5016"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}