Skip to content
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

Open
DiegoPino opened this issue May 19, 2020 · 6 comments
Open

Drupal 9 Readiness check before June 3rd #54

DiegoPino opened this issue May 19, 2020 · 6 comments
Assignees
Labels
Drupal9 Drupal9 is the new Drupal8 which was the new Drupal7 wich was the... help wanted Extra attention is needed
Milestone

Comments

@DiegoPino
Copy link
Member

DiegoPino commented May 19, 2020

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

@DiegoPino DiegoPino added this to the 1.0.0-beta3 milestone May 19, 2020
@DiegoPino DiegoPino added Drupal9 Drupal9 is the new Drupal8 which was the new Drupal7 wich was the... help wanted Extra attention is needed labels May 19, 2020
@DiegoPino
Copy link
Member Author

DiegoPino commented May 22, 2020

And i start today! I'm so proud of myself 🏷️
I will check SBF first and go from there.

@DiegoPino
Copy link
Member Author

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

@pcambra
Copy link

pcambra commented Feb 9, 2021

I've done a fast quick pass on the required modules from composer.json:

  Problem 1
    - drupal/display_field_copy dev-1.x requires drupal/core ~8.0 -> found drupal/core[8.0.0-beta6, ..., 8.9.x-dev] but it conflicts with your root composer.json require (9.1.4).
    - drupal/display_field_copy 1.x-dev is an alias of drupal/display_field_copy dev-1.x and thus requires it to be installed too.
    - Root composer.json requires drupal/display_field_copy 1.x-dev -> satisfiable by drupal/display_field_copy[1.x-dev (alias of dev-1.x)].


  Problem 1
    - drupal/form_mode_manager dev-2.x requires drupal/core ^8 -> found drupal/core[8.0.0-beta6, ..., 8.9.x-dev] but it conflicts with your root composer.json require (9.1.4).
    - drupal/form_mode_manager 2.x-dev is an alias of drupal/form_mode_manager dev-2.x and thus requires it to be installed too.
    - Root composer.json requires drupal/form_mode_manager 2.x-dev -> satisfiable by drupal/form_mode_manager[2.x-dev (alias of dev-2.x)].

  Problem 1
    - drupal/key_value dev-1.x requires drupal/core ^8 -> found drupal/core[8.0.0-beta6, ..., 8.9.x-dev] but it conflicts with your root composer.json require (9.1.4).
    - drupal/key_value 1.x-dev is an alias of drupal/key_value dev-1.x and thus requires it to be installed too.
    - Root composer.json requires drupal/key_value 1.x-dev -> satisfiable by drupal/key_value[1.x-dev (alias of dev-1.x)].

  Problem 1
    - drupal/role_theme_switcher dev-1.x requires drupal/core ^8 -> found drupal/core[8.0.0-beta6, ..., 8.9.x-dev] but it conflicts with your root composer.json require (9.1.4).
    - drupal/role_theme_switcher 1.x-dev is an alias of drupal/role_theme_switcher dev-1.x and thus requires it to be installed too.
    - Root composer.json requires drupal/role_theme_switcher 1.x-dev -> satisfiable by drupal/role_theme_switcher[1.x-dev (alias of dev-1.x)].


  Problem 1
    - drupal/webform_entity_handler dev-1.x requires drupal/core ^8 -> found drupal/core[8.0.0-beta6, ..., 8.9.x-dev] but it conflicts with your root composer.json require (9.1.4).
    - drupal/webform_entity_handler 1.x-dev is an alias of drupal/webform_entity_handler dev-1.x and thus requires it to be installed too.
    - Root composer.json requires drupal/webform_entity_handler 1.x-dev -> satisfiable by drupal/webform_entity_handler[1.x-dev (alias of dev-1.x)].

Modules allegedly incompatible with Drupal 9:

@DiegoPino
Copy link
Member Author

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

@DiegoPino
Copy link
Member Author

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!!!

@DiegoPino
Copy link
Member Author

role_theme_switcher: we may either roll with a single theme better OR explore alternative modules.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Drupal9 Drupal9 is the new Drupal8 which was the new Drupal7 wich was the... help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants