And we couldn’t be more excited! In fact, we are already working on two sites to launch early 2016 in Drupal 8.
Eight reasons why Drupal 8 rocks!
- Mobile in its DNA
- Multilingual Capabilities
- New Configuration Management
- Accessibility Integration
- A Better User Experience
- Built-In Web Services
- Effortless Authoring
- Fun and Fast Theming
So guess what Drupal 6 sites… it really is TIME to update!
“Drupal 6 core and modules will transition to unsupported status three months after Drupal 8 is released. “Unsupported status” means the community will not be providing support or patches in the same way we do now. Continuing to support Drupal 6 would be difficult for many reasons, including a lack of automated test coverage, the requirement for rigorous manual release testing, the slow-down it introduces in the release of security fixes for the vast majority of Drupal users (on version 7+), and the general shift of volunteers in the community moving their attention onto Drupal 8 development.
This gives Drupal 6 users a few options:
1) Upgrade to Drupal 7 any time between now and 3 months after Drupal 8.0.0 is released. Drupal 7 releases undergo almost 40,000 automated tests, and Drupal 7 will be fully supported at least until Drupal 9 comes out. Given the past history, the release of Drupal 9 is likely to be around 2018.
2) Upgrade to Drupal 8 after it is released, but before Drupal 6 is not supported anymore. Fortunately, Migrate support for Drupal 6 to Drupal 8 is already in core, and there is Migrate UI, a contributed module. While not all contributed modules will be ready at the time Drupal 8 is released, Drupal 8’s migration path handles most of the critical site data via its CCK to Entities/Fields in Core migrations.
3) Find an organization that will provide extended support for Drupal 6. The Drupal Security Team will provide a method for companies and/or individuals to work together in the private security issue queue to continue developing updates, and will provide a reasonable amount of time for companies to provide patches to Drupal 6 security issues that also affect Drupal 7 or Drupal 8. The security team will coordinate access to issues for companies wishing to provide extended support for Drupal 6. However, the team will not explicitly review or test the patches (some team members may do this on their own). All code created by these vendors, would be released to the community.” (from Drupal.org)
Then, if you are ready for a remodel, give us a call and we can all say together “We want Drupal 8!”