Recently, the Springloops version control system made its debut on the web and was greeted with both skepticism and interest. One developer, Hasin Hayder decided to look at it from a different angle and worked to see how easy it would be to reproduce a similar service.

Springloops is a nice code management service recently came into focus. It helps you to manage the code base of your application, monitor the commit and deploy the final version easily to another server. So if you are wondering how to build such a system and how it actually works, this article is for you.

He breaks it down into the six main topics (as he sees it) that are the core parts of the system - things like payment gateways, setting up subversion and making it user friendly. He goes through each topic, explaining its place in the application and providing some links to resources to help you set it up (or at least learn more about it).

On the Version Control Blog today there's a new guide that helps to make upgrading your Drupal installation a simple and happy experience with the help of git (the version control system).

Drupal development team has released Drupal 5.2 on July 26, 2007. It fixes two security vulnerabilities, so it is highly recommended that you upgrade as soon as possible. Many Drupal installations often contain extra Drupal modules, and almost always the also contain local customizations.

Question arises: how to upgrade your Drupal installations timely, safely, with confidence that none of your local customizations are lost; without need to remember each line that was edited and re-applying those edits to new version and without need to drastically change your workflow (very little discipline is needed actually).

This detailed guide walks you through the import of the source code, import of the Drupal modules and making the upgrades to the installation (drupal, drupal-and-modules and drupal-production) as well as how to resolve conflicts that might come up.