There are a lot of ways to help out to speed up the overall process. If you are done with all of your custom code and low-hanging fruit, dedicate some time inside the issue queues of contrib modules your website depends on. Keep your contrib module inventory up to date during your transition period. By the time you get to them later, it may be a trivial update. This allows time for some of the more difficult contrib work to be completed by the module maintainers and the wider community. This is where you want to start.įocus on your custom modules and the easy contrib updates first. That represents the lowest level of effort. There is no substitute for rolling up your sleeves and getting to work.įor contrib modules, the latest releases will often support both Drupal 8 and Drupal 9, so they can go ahead and be updated. Start adding some of the tickets you created into your sprints or general workload. Updating modules and codeįixing your custom codebase is all work you are going to have to do sooner or later. Many projects won’t require any changes, but it is best to check early so you are not surprised.Īdd any flags as tickets to your ticketing system. The Upgrade Status module should flag these for you. Make sure your templates are not using functions in Twig templates that are not supported in version 2. Twig has its own deprecations moving from Twig 1 to Twig 2. If you use any contrib base or sub-themes, keep them on your list to track and treat them as modules.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |