Sometimes they aren’t seen again until close to launch. With the old Drupal upgrade model, there was a risk of the dreaded stakeholder swoop: someone swoops in, lists a bunch of requirements without regard to overall goals and priorities and swoops back out. Ideally, with a more iterative approach to development, stakeholders stay more involved and informed, and therefore better discussions can be had around the website. Promote any new features that were rolled out by these updates.These should be just as visible as other initiatives that are being developed and be treated as equally important. This might mean a sprint every month or so 100% dedicated to updates. These should be scheduled from the top by project managers. Schedule updates ahead of time, and do not let the desire for new features cannibalize these dates.Not only for Drupal 9 but also for any contributed modules and other software that is part of your hosting stack. Build a schedule of releases and support windows for your software.Our article on Drupal 8 release planning is still relevant for Drupal 9. With this, you also have the possibility of getting new features that have been included, and you should be aware of them. To get the latest security updates, you need to stay on the latest minor point release (9.1, 9.2, etc.). Like Drupal 8, Drupal 9 requires frequent updates. And you need to maintain what you have at a sensible pace. Having this large, common goal that everyone sees with clarity can make a lot of this stuff come more easily, but now, you need to figure out how to create and harness these things while not depending on the existence of a monolithic target that dominates the landscape. It draws out intention, direction, and sometimes enthusiasm, and none of these are bad things to have. It acts as a huge celestial star, with everything else gradually falling into orbit around the big initiative. One good thing about major re-platforming efforts is that they have to be planned for in advance. In this brave new world where upgrading to the next major Drupal release isn’t a big re-platforming effort, what does web development strategy look like? Establish a cadence for web development work Your relationship with outside vendors will take on a new cadence. ![]() When it comes to your Drupal website, your organization will need to begin running a marathon that goes on for years. You will need to shift your own thinking and habits. Keeping your platform up-to-date with the next version is no longer an “all hands on deck” situation.Īs with all changes, however, this new model comes with its own challenges and problems. The first iteration of Drupal 9 is just Drupal 8 with all of the deprecated code removed, mimicking Symfony’s model of major release upgrades. The big change is that…your organization’s website won’t require a big change. The Drupal 8 to Drupal 9 upgrade path represents a big change for the Drupal world.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |