-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drupal 9 Readiness check before June 3rd #54
Comments
And i start today! I'm so proud of myself 🏷️ |
General info here just in case someone wonders what is the status? D9 since forever!. @giancarlobi has D9 and Archipelago running live already. There are some minor changes that needed to be done (that escaped my automated deprecation check and some other contributed modules annoyances but all is well). All that went into 1.0.0-RC1 of each module. Conclusion 1.0.0-RC1 will be dual version either 8.9.5 or 9.0.4 up to you |
I've done a fast quick pass on the required modules from composer.json:
Modules allegedly incompatible with Drupal 9:
|
This is great @pcambra. display_field_copy 2.0.0 is nice, I was not even aware of it. Form mode manager is a larger issue, we may try to ask for maintenance roles there if there is no movement or take over some of the functionality into webform_strawberryfield |
Also the webform_entity_handler is something we really do not need for any standard implementation. We may explore it again in the near future (or in a call!) and helps a lot you are in charge!!! |
role_theme_switcher: we may either roll with a single theme better OR explore alternative modules. |
What? Drupal 8 is death (or will be by June 3rd.. ok it's not like that really), long live Drupal 9 (also, will be a just born one, full of bugs...so)
Yep. It took us some time, like almost 2 years from idea to what we have now and we designed Archipelago to be as compliant to Drupal 9 as we could with such a tiny team and too little time. Still, codebase has grown, we have so much good and complex too code, so we need to pass a general review on each Module we coded but also on each module we suggest should be used. This Issue will be a placeholder for this Friday, when that work will be passed. Idea is to check here what passed and open the issues needed to make the other ones pass. And then have (yes!) a 9.x-1.0 branch for our very own and of course more code to maintain... help!.
@giancarlobi @mitchellkeaney
The text was updated successfully, but these errors were encountered: