An important upgrade has happened – Mercurial Support for Versionshelf!

With the updated server infrastructure we also introduced a significant new feature: Mercurial Support. Mercurial is one of the emerging Distributed Version Control Systems. Used by great projects like Sun OpenSolaris or the Python language it has proven to be one of the best of its breed – and to us even more important: we love it!

Usage is quite similar to Subversion, but follows the more and more popular approach of distributed version control systems: every working copy is also the complete repository with the whole history. Commits go to your local repository – even when you are not online. To keep your repository in sync with others you push and pull to/from a central repository.

To make collaboration in your projects an easy experience, Versionshelf now supplies the central place for Mercurial repositories.

Beyond Mercurial Support we also made existing features even better: post commit hooks and the activity view.

We hope you enjoy these changes!

If you are not already a Versionshelf user you may have a look at our plans and features.

Today we upgraded our subversion servers to the latest version – 1.6.1.
The new subversion features like tree conflict resolution and enhanced merge tracking are therefore finally available to our customers (Release Notes 1.5, 1.6).

Existing repositories have not been updated automatically to make sure that older clients and tools keep working. To take advantage of the new features you should upgrade all your clients to their latest versions.

If you would like to update your repositories, just login as admin to your Versionshelf. There you find the upgrade notification with a link that allows you to upgrade all your repositories with a single click.

All new repositories are created with the new 1.6.1 subversion repository format.

If you experience any problems, please don’t hesitate to contact us at support [at] versionshelf.com!

Today we increased the basic data of all our plans by quite some magnitude:

• Personal Plan
  Storage +500MB, Repositories +4
• Basic Plan
  Storage +2.5GB, Repositories +10, Accounts +10
• Plus Plan
  Storage +6GB, Repositories +10, Accounts +25
• Premium Plan
  Storage +10GB

Hopefully you find the increased specs useful and many thanks for being our customers!
If you are not already a Versionshelf user you may have a look at our plans and features.

A hidden feature that is implemented for some time now but never officially announced is rendering of textile, markdown and rdoc documents in our subversion repository browser.

Textile, Markdown and RDoc allow you to format text with a lightweight and easy to use markup language.

As with syntax highlighting it just seems more natural to see textile and markdown documents rendered as they should. See the two screenshots below:

The first picture shows the rendered textile content, the other the regular source view.

Let’s say you have a textile formatted README file in your project and want it to be rendered as html in the repository browser, you just need to add an svn property named vsrender to the file. Eg. execute svn propset vsrender textile README in your shell.

We support Textile, Markdown, RDoc and a simple text view. The corresponding vsrender-properties are named as follows:

• textile
• markdown
• rdoc
• simple_format

If you would like to see the actual source of the rendered file you can just switch to the regular source view as shown below:

With this feature our repository browser can almost be used as a simple wiki (which was our initial intention :)!

Our Versionshelf svn browser can now display source code with syntax highlighting.

The screenshot below shows the syntax highlighting of a java file.

So far we support syntax highlighting for the following source types:

• C
• C++
• Java
• PHP
• Ruby
• RHTML
• HTML
• Javascript

Due to popular demand we made the sender address of the notification email post commit hook editable.

If you leave the sender address field blank, the sender email address is automatically set to the one of the receiver.