After much work, I've finally been successful in upgrading this blog to Drupal 6. This is the third attempt, and the first one that wouldn't have had me editing the database to fix the bork-ups that 'upgrading' modules between versions created. All of this caused me to remember why I was hesitant to upgrade before now.

Version 6 should not have been released without a fully-functional views and cck modules, and without good documentation on what changed. Up until some months ago, the Form API reference for drupal 6 was essentially here's the 5.x version: in order to use it for 6.x here's a massive list of errata. Not acceptable.

So, close to two years later D6 has decent documentation. It felt rushed, and didn't have what it needed to be usable by a large population of developers. Drag-and-drop rearrangement of weighted items is eye candy and not enough to justify a major release that destroys backwards-compatibility.

Fortunately, version 5 is still supported with security updates. But much new module development has halted, which is very unfortunate for some. With the release of D7, 5.x will no longer be officially supported, and there are a lot of 5.x sites remaining 'in the wild'. Drupal 7 looks good, and I hope it

Yet, the code freeze for version 7 was in September. With talk of this code freeze lasting six months or more, there is promise. One year between the release of version 5 and version 6 was too soon. The lack of a functional views module on release was a big sticking point for many people, but it was not the main issue I had with D6.

BTW, There is a views 7.x development version.