![]() The number of depreciations reduced gradually using this approach and the Thunder code base currently shows around 130 deprecations. That was our to do list for the coming weeks.Īs soon as a patch existed or had been committed to a dev branch (by us or someone in the community) we adjusted the pull request above with these patches and dev versions – and ran the test again. We collected all of these issues – both those created by us and by others – in a Thunder META issue in order to stay on top of things. ![]() If there was no issue we created it and worked on a patch ourselves.In some instances issues had already been created on which we could work by checking patches or helping to develop them.In the best case there are already patches which, although they are yet to be released, have been been committed in the dev branch.We have now gone through it all module by module and checked whether an issue for removing the deprecated code was present in the issue queue and what the status quo is: However: After the first successful run in December we discovered that our current Thunder codebase exhibited depreciated code requiring removal or replacement in 500 different areas. Ideally the modules are completely up to date and don’t even pop up in our test. Instead of our usual tests, we have put together a git branch for this purpose which checks all modules used in Thunder for deprecated code. We hope we are able to help you to get your sites ready for Drupal 9 and look forward to hearing about your experiences and tips!ġ) How does a distribution become compatible with Drupal 9?įirst of all it is a question of recognising which modules and which areas have deprecated code in need of removal. Our approach can not only serve as inspiration to distribution operators but also to anyone currently operating a Drupal site. We are convinced that this overview can help everyone who is currently dealing with the topic of Drupal 9. We want to show you in the following blog how the Thunder team has proceeded and how we continue to work: How do we establish where we are and which actions are required? How do we proceed with module updates? And what remains to be done? Starting in December, our objective is to get every module onto as current a version as possible so that we can begin with the testing. We have developed an approach for systematically going through all modules, recognising any required actions and working together with the module operators. We are faced with the challenge of making our own distribution with around 60 modules compatible of Drupal 9 – recognising all dependencies, keeping everything running at the same time and ensuring everything is ready by June. We in the Thunder team have also asked ourselves this question. ![]() Those of you who have started the new year well prepared, run all updates and do not use older modules are off the hook. In the ideal scenario you won’t even notice. It is expected to be ready by June – Drupal 9 is coming.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |