Version Control

Why Drupal.org lacks good themes (and why CVS has nothing to do with it)

What CVS does to (some) designersWhat CVS does to (some) designers

There’s been a lot of talk lately about how Drupal designers shouldn’t have to learn CVS. Nothing new to see here, really — just the same tired, self-fulfilling arguments about how much CVS sucks, how developers also hate using it, and how designers shouldn’t be expected to learn something so… technical.

Bazaar 1.16 RPMs for RHEL 5 and CentOS 5

Fresh packages, 64-bit only. There are release notes for the curious.

Bazaar 1.14 RPMs for RHEL 5 and CentOS 5

Fresh packages, 64-bit only (again). I can make 32-bit ones if anyone would like some. I’d say that this is the most exciting release yet.

Alternatives to rebasing in Bazaar

A discussion recently arose on the Bazaar mailing list asking, “Why isn’t rebase support in core?” Rebase support is currently packaged as a plugin. This plugin is widely distributed, even in the standard Mac OS X installation bundle.

There are boring reasons that rebase support isn’t in core, like the lack of strong test coverage. More interesting are questions about the necessity of rebasing in typical workflows.

What is rebasing, and why should I care?

In large projects, there’s a mainline branch representing the current, global, coordinated development. In Drupal’s case, this is CVS HEAD. This mainline might not always be in perfect condition, but there’s a general sense that the mainline is not a sandbox for untested changes. Many changes are small enough that the developers simply work on and test a patch, but this workflow is inadequate for larger development projects like Fields in Core. Such large features require their own branch for development, a feature branch.

Contact Four Kitchens

Pressflow makes Drupal scale