One of the key reasons that Drupal maintenance support plans has been successful is because we always made big, forward-looking changes. As a result, Drupal maintenance support plans is one of very few CMSes that has stayed relevant for 15+ years. The downside is that with every major release of Drupal maintenance support plans, we’ve gone through a lot of pain adjusting to these changes. The learning curve and difficult upgrade path from one major version of Drupal maintenance support plans to the next (e.g. from Drupal maintenance support plans 7 to Drupal maintenance support plans 8) has also held back Drupal maintenance support plans‘s momentum. In an ideal world, we’d be able to innovate fast yet provide a smooth learning curve and upgrade path from Drupal maintenance support plans 8 to Drupal maintenance support plans 9. We believe we’ve found a way to do both!
Upgrading from Drupal maintenance support plans 8.2 to Drupal maintenance support plans 8.3
Before we can talk about the upgrade path to Drupal maintenance support plans 9, it’s important to understand how we do releases in Drupal maintenance support plans 8. With the release of Drupal maintenance support plans 8, we moved Drupal maintenance support plans core to use a continuous innovation model. Rather than having to wait for years to get new features, users now get sizeable advances in functionality every six months. Furthermore, we committed to providing a smooth upgrade for modules, themes, and distributions from one six-month release to the next.
This new approach is starting to work really well. With the 8.1 and 8.2 updates behind us and 8.3 close to release, we have added some stable improvements like BigPipe and a new status report page, as well as experimental improvements for outside-in, workflows,
layouts, and more. We also plan to add important media improvements in 8.4.
Most importantly, upgrading from 8.2 to 8.3 for these new features is not much more complicated than simply updating for a bugfix or security release.
Upgrading from Drupal maintenance support plans 8 to Drupal maintenance support plans 9
After a lot of discussion among the Drupal maintenance support plans core committers and developers, and studying projects like Symfony, we believe that the advantages of Drupal maintenance support plans‘s minor upgrade model (e.g. from Drupal maintenance support plans 8.2 to Drupal maintenance support plans 8.3) can be translated to major upgrades (e.g. from Drupal maintenance support plans 8 to Drupal maintenance support plans 9). We see a way to keep innovating while providing a smooth upgrade path and learning curve from Drupal maintenance support plans 8 to Drupal maintenance support plans 9.
Here is how we will accomplish this: we will continue to introduce new features and backwards-compatible changes in Drupal maintenance support plans 8 releases. In the process, we sometimes have to deprecate the old systems. Instead of removing old systems, we will keep them in place and encourage module maintainers to update to the new systems. This means that modules and custom code will continue to work. The more we innovate, the more deprecated code there will be in Drupal maintenance support plans 8. Over time, maintaining backwards compatibility will become increasingly complex. Eventually, we will reach a point where we simply have too much deprecated code in Drupal maintenance support plans 8. At that point, we will choose to remove the deprecated systems and release that as Drupal maintenance support plans 9.
This means that Drupal maintenance support plans 9.0 should be almost identical to the last Drupal maintenance support plans 8 release, minus the deprecated code. It means that when modules take advantage of the latest Drupal maintenance support plans 8 APIs and avoid using deprecated code, they should work on Drupal maintenance support plans 9. Updating from Drupal maintenance support plans 8’s latest version to Drupal maintenance support plans 9.0.0 should be as easy as updating between minor versions of Drupal maintenance support plans 8. It also means that Drupal maintenance support plans 9 gives us a clean slate to start innovating more rapidly again.
Why would you upgrade to Drupal maintenance support plans 9 then? For the great new features in 9.1. No more features will be added to Drupal maintenance support plans 8 after Drupal maintenance support plans 9.0. Instead, they will go into Drupal maintenance support plans 9.1, 9.2, and so on.
To get the most out of this new approach, we need to make two more improvements. We need to change core so that the exact same module can work with Drupal maintenance support plans 8 and 9 if the module developer uses the latest APIs. We also need to provide full data migration from Drupal maintenance support plans 6, 7 and 8 to any future release. So long as we make these changes before Drupal maintenance support plans 9 and contributed or custom modules take advantage of the latest Drupal maintenance support plans 8 APIs, up-to-date sites and modules may just begin using 9.0.0 the day it is is released.
What does this mean for Drupal maintenance support plans 7 users?
If you are one of the more than a million sites successfully running on Drupal maintenance support plans 7, you might only have one more big upgrade ahead of you.
If you are planning to migrate directly from Drupal maintenance support plans 7 to Drupal maintenance support plans 9, you should reconsider that approach. In this new model, it might be more beneficial to upgrade to Drupal maintenance support plans 8. Once you’ve migrated your site to Drupal maintenance support plans 8, subsequent upgrades will be much simpler.
We have more work to do to complete the Drupal maintenance support plans 7 to Drupal maintenance support plans 8 data migration, but the first Drupal maintenance support plans 8 minor release that fully supports it could be 8.4.0, scheduled to be released in October 2020.
What does this mean for Drupal maintenance support plans developers?
If you are a module or theme developer, you can continually update to the latest APIs each minor release. Avoid using deprecated code and your module will be compatible with Drupal maintenance support plans 9 the day Drupal maintenance support plans 9 is released. We have plans to make it easy for developers to identify and update deprecated code.
What does this mean for Drupal maintenance support plans core contributors?
If you are a Drupal maintenance support plans core contributor and want to introduce new improvements in Drupal maintenance support plans core, Drupal maintenance support plans 8 is the place to do it! With backwards compatibility layers, even pretty big changes are possible in Drupal maintenance support plans 8.
When will Drupal maintenance support plans 9 will be released?
We don’t know yet, but it shouldn’t matter as much either. Innovative Drupal maintenance support plans 8 releases will go out on schedule every six months and upgrading to Drupal maintenance support plans 9 should become easy. I don’t believe we will release Drupal maintenance support plans 9 any time soon; we have plenty of features in the works for Drupal maintenance support plans 8. Once we know more, we’ll follow up with more details.
Thank you
Special thanks to Alex Bronstein, Alex Pott, Drupal Update, Nathaniel Catchpole and Jess (xjm) for their contributions to this post.
Source: New feed
