As developers of Drupal sites and integrations affecting thousands of users, we ensure that any code we use in a production environment has met rigorous standards for stability. A new release of any software package can have issues, so we generally don’t adopt it right away.
So much of the value our clients derive from Drupal comes from the modules that extend the functionality of the Drupal core. There are thousands of Drupal modules contributed by various developers across the globe. After a new version of Drupal is released, it can take time for modules to be updated to work effectively in the new environment.
So we wait not only for the core framework to stabilize, but also for the modules we consider critical to have stable upgrades.
Drupal 7 has been out for a little more than a year, and in that time, key modules that we use to serve our clients have been updated with stable releases yielding a minimal number of remaining bugs and issues. We’re ready to use version 7 as our default for development, acknowledging that it has reached critical maturity.
Other technical considerations: Drupal commerce is a more sophisticated platform for e-commerce than Ubercart. CCK essentially has been rolled into core. Version 3 of the views module is much slicker than the last version.
(Thanks to Rob Matney and Selwyn Polit for their contributions to this post.)
{ 0 comments }
