![]() Is that a position you want to be in? Should you take the risks now and the potentially slower development time associated with Drupal 7, so you don’t have to pay for a whole new site just to upgrade yours from Drupal 6 to Drupal 7 when Drupal 6 has fallen by the wayside? With this in mind, should you install Drupal 6 when the Drupalverse is moving toward Drupal 7? Once the scales shift in favor of Drupal 7, Drupal 6 support is likely to decline rapidly. Often, I find that the work estimate for starting the site with a clean installation of the new Drupal core version and migrating the data myself is the same or even less than the estimate to upgrade the site and fix everything that goes wrong. The more contributed modules you use on your site, the more of a headache it is. Drupal 5 to Drupal 6 or Drupal 6 to Drupal 7, is known to be a headache. Upgrading across Drupal core versions, i.e. The final consideration between Drupal 6 and Drupal 7 is the upgrade path or migration route. The number of reported installations of Drupal 7 has already grown by 130% since the beginning of the year. If this rate continues linearly, by the end of the year there will be around 52, 000 reported installations of Drupal for a total increase of around 232% since the initial Drupal 7.0 release. That’s a 2.2 average percent increase per week of reported installations since the 7.0 release of Drupal 7. Over the first 25 weeks, almost 6 months, of 2011, Drupal 7 has grown at an average of 618 reported installations a week. How quickly is Drupal 7 growing, though?Ĭlick the image to see the larger version of the Drupal 7 growth chart. Now, it really seems like Drupal 6 is the answer to the question of which version of Drupal should I use. ![]() That’ s a lot of people still working on Drupal 6 modules and not working on Drupal 7 modules. That’s a lot of people who still need Drupal 6 modules developed. That’s a lot of people who still need Drupal 6 support. That’s a lot of people still using Drupal 6. Out of the total reported installations (275, 980), 87% of the installations are Drupal 6. These three releases range from Januto May 25, 2011. As of June 19th, there are 36, 118 reported installations of Drupal 7. For Drupal 7, there are currently three releases out of alpha, beta, and release candidate stages that have usage statistics: 7.0, 7.1, and 7.2. These four releases range from Augto May 25, 2011. This number comes from the usage statistics on the last four releases of Drupal 6: 6.19, 6.20, 6.21 and 6.22. Even after all these months, is Drupal 6 still the version of Drupal you should use on your project? As of June 19th, there are 239, 862 reported installations of Drupal 6. So, it seems that the answer to the question is Drupal 6. That’s not to say that the time to develop the project becomes abnormal, but rather, the time to develop the project is no longer shortened by using Drupal. ![]() ![]() ![]() If the Drupal modules you want to use for a project aren’t available in Drupal 7, development time on the project could easily be tripled. Drupal modules allow for rapid web development, potentially without programming. The best part about Drupal is that you assemble sites. I also knew that the module base was not going to be very large. I knew that there were going to be some releases of the Drupal core with security fixes. When Drupal 7 was first released, I steered clear of using it for any of our projects at Accella. The new…news, however, is that you should begin asking this question: Should I go with Drupal 6 or Drupal 7? Drupal Version 7? How would this work in conjunction with the core_version_requirement key, as I believe semver is only supported starting from Drupal 8.7.With the release of Drupal 7 on January 5th of this year, there’s a new consideration in the mix for building Drupal sites. So would I switch to a new branch 3.x and tag 3.0.0, or can this tag be on the same 8.x-2.x branch as they are essentially running the same codebase? Otherwise I have to apply all bug fixes and changes onto 2 branches. My module for example is considered compatible for both Drupal 8 and 9, tagged with a release 8.x-2.1 on branch 8.x-2.x. While I do understand that we need to tag these branches & releases incrementally based on your current 8.x version, how is this taken into practise? I have read a little bit about using semver for contrib modules in the updated documentation Transitioning from 8.x-* to semantic versioning and release version numbers allow semantic versioning. ![]()
0 Comments
Leave a Reply. |