Guymon

Updating Drupal using SVN

Chris Geoghegan beschreibt Updating Drupal using SVN Vendor Branches.

This tutorial will show you how to setup Drupal as vendor branch in your subversion repository. This will allow you to apply changes that are made between versions without losing or overwriting contributed modules or patches that you may have made to your install of Drupal. In fact, if your working on multiple Drupal projects you can have them all share the same base and security updates can be rolled out much easier.

Das Tutorial ist leicht verständlich - noch eine Drupal/SVN Variante zum testen.

Drupal CVS/SVN Setup

Was zum gucken:

This content is very much on the geeky side. It outlines using the CVS/SVN combination which many of the top Drupal developers use. In this video, I outline my repository structure and how I deploy my Drupal code. The first half provides an intro with links to stuff you need to know about CVS and SVN, and the later walks through some of the details of how it all works.

Git Resources

Here is a list of six resources that will help you get more comfy with Git, whatever your current knowledge of the tool.

Zu finden bei nexus.

Springloops - Source Code Management

Springloops werde ich morgen auf der Arbeit mal ausprobieren - hört sich interessant an, mal sehen was es tatsächlich kann.

Springloops is a unique source code management tool focused on web development teams. It allows you to code in parallel and share your code safely concentrated on results, not on lost changes or overwritten files. You get rapid collaboration in protected space. Thanks to the project management perspective it serves the getting things done attitude. Moreover, Springloops reduces repeatable activities in your day-to-day work.

It makes great things simple.

Visual Guide to Version Control

Eine recht gute Einführung in die Konzepte der Versions Kontrolle gibt es bei BetterExplained.

My goal was to share high-level thoughts about version control systems. Here are the basics:

• Use version control. Seriously, it’s a good thing, even if you’re not writing an OS. It’s worth it for backups alone.
• Take it slow. I’m only now looking into branching and merging for my projects. Just get a handle on using version control and go from there. If you’re a small project, branching/merging may not be an issue. Large projects often have experienced maintainers who keep track of the branches and patches.
• Keep Learning. There’s plenty of guides for SVN, CVS, RCS, Git, Perforce or whatever system you’re using. The important thing is to know the concepts and realize every system has its own lingo and philosophy. Eric Sink has a detailed guide as well.