BoootStrapToday Subversion Server to be upgraded to1.7 soon

It’s been over two months since the Subversion 1.7 release was announced, since than there have been two bug fix releases and the bug & error reporting on the mailing list has gone down, It seems like right time for BootStrapToday Subversion server to be upgraded to 1.7.

So what to expect from this upgrade

  • Improved performance of Subversion over http  : performance of Subversion over http has been one of the major concerns of Subversion community since early releases, Subversion 1.7 hits this problem right on head by introducing httpv2, PROPFIND discovery turnarounds have been removed and reduced number of round trips for a request, also there is better caching with web proxies, this was one of the most awaited feature by Subversion community as a whole.
  • SVNRDUMP: Subversion 1.7 adds a new tool to the client’s toolbox, svnrdump replicates the functionality of svnadmin dump and svnadmin load, but works on remote repositories, instead of needing administrator access to the source or target repository, this would allow users to migrate repositories with ease from other sources to BootStrapToday
  • Subversion 1.7 has taken caching to next level, 1.7 servers will aggressively cache data in-process to maximize performance.svnserve introduces a new --memory-cache-size / -M command line parameter to override the default cache size. Same  can be configured in Apache server as mentioned below
          <IfModule mod_svn_module>
             SVNInMemoryCacheSize 10240
          </IfModule>
      

With 1.7 server you will still be able to use your Subversion 1.6 clients.  However, we recommend that you upgrade to a Subversion 1.7 clients, because many operations will be faster.

We will update you on upgrade plan soon, we are thinking to utilize christmas holidays to do it, let us know your thoughts on same.

Enhancement in BootStrapToday Release 2.0

Following are some of the new enhancements in this Release

1) GIT support has been added.

Every Project you create in BootStrapToday has its own repository. So now while creating a new Project you can choose between SVN and GIT.

2) Login Page redesigned.

We felt the need to redesign the login page as per the design of the application, so we have pushed that as well in this release.

3) Ticket delete

Ticket delete feature has been added. This action will be available only to Project Manager.

4) Quick Ticket Edit

We had added “Quick Create” in the last release and in this we have also added “Quick Edit” functionality. This will be available in both Ticket list view as well as Milestone detail view. Now user can quickly edit multiple tickets from the same view without going through the different screens.

Campaign on SVN Vs GIT Usage

BootStrapToday currently supports Subversion as a version control for code and document versioning. As per data Subversion still commands 36% of the market share, which is by far greater than any other Version control software.  So we had assumed most of our customers will also fall in this category.

But recently there were some request from our customers and prospects for supporting GIT as well. We ran a small campaign with our existing customers and on linkedin before integrating GIT with BootStrapToday. We were aware about the trend of migration to distributed version control from centralized one, but to our surprise, results were astonishing. Please find the result of the campaign in the chart below.

SVN Vs GIT

This clearly states that people are more inclined towards GIT. So our initial assumptions were proved wrong.

So finally we will be supporting GIT in the April, 2011 end release. Thanks for your patience and support.

What Subversion 1.7 has in Store for You ?

It’s been a while I have been hearing about Subversion 1.7, which is finally expected to be released in Q1 of 2011 as per roadmap available here, it’s expected to be one of the biggest release in the history of Subversion.

So what to expect from Subversion 1.7?

In this post I am going to talk about some of the key features and enhancement which I have been waiting for, which is going to make my argument stronger on why you should use Subversion.

  • WC-NG : It is the rewrite of working copy library,the .svn directories will be eliminated and there will be one big .svn directory in Working Copy root. Today Subversion takes something between 10 sec to 2 minutes to start after you enter svn command (svn info, svn up, etc…) that occurs because each .svn metadata directory will be read from the local disk first. That will no longer be the case, after WC-NG is introduced.
  • HTTPV2 : Increases performance of Subversion over http, this is going to remove PROPFIND discovery turnarounds and reduced number of round trips for a request, this also going to include better caching with web proxies.
  • 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.
  • SVNRDUMP:Subversion 1.7 adds a new tool to the client’s toolbox: svnrdump. svnrdump replicates the functionality of svnadmin dump and svnadmin load, but works on remote repositories, instead of needing administrator access to the source or target repository.
  • Server performance tuning: Subversion already support various caching mechanism like memcached, Subversion 1.7 is set to take caching to next level, 1.7 servers will aggressively cache data in-process to maximize performance.svnserve introduces a new --memory-cache-size / -M command line parameter to override the default cache size. Same  can be configured in Apache server as mentioned below

          <IfModule mod_svn_module>
             SVNInMemoryCacheSize 10240
          </IfModule>