-
Notifications
You must be signed in to change notification settings - Fork 44
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 10 compatibility. #761
Comments
Running Result
|
Thank you for identifying the issues and sharing the information. I can create individual separate issues for each one of these changes. I will use the label "Drupal 10 Preparation" for this. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@giteshk Hi, is there a timeline that you can share publicly for adding D10 compatibility to this module? Thanks in advance. |
We have started work on this, tracking to end of Q2 2023. You will start seeing issues being created in the next 2 weeks. Feel free to add any tickets with "Drupal 10 Preparation" label. |
Thanks for the quick reply Gitesh!
Q2 has just started, Drupal 10.0.0 is out since December 14, 2022. Drupal 9.5's support end on November 1, 2023. These dates means to me that Drupal 10.0.x should be fairly stable now and if companies do not want to wait until the final call to upgrade their sites to security covered new major version (that also requires PHP 8.1) they should do that either in Q2 or Q3. In other words, can the Apigee team make this a higher priority? Regarding contributions, @VladimirAus has already opened the #782. I have spent some time reviewing that back in the day but I see no other feedback on it. |
I agree with @mxr576 that customers (and vendors) should be given a chance to test the update in Q2 - because if it's postponed to Q3 then by the time things reach production we could already be in Q4 🙀 |
To add the chorus here: I help maintain a large site that relies on this module, and it is the only main blocker keeping us from being able to upgrade our multi-site to Drupal 10. For us, it would be ideal if this was already a Drupal 10 release. |
All PRs I did for Apigee Drupal modules in the last 3 years were either stolen by internal Google team (I never got a credit) or forgotten, so no surprises here 🤷♂️ |
Hey @VladimirAus , that's pretty strong language! If you're serious about your allegations of "stolen code," I'd be happy to review examples where you have some grievance, and then to address where changes might be necessary. But let's find a way to do that that doesn't pollute this issue, which is meant to address Drupal 10 compatibility? And thanks, everyone, for your input on how important it is to enable upgrades to Drupal 10. We hear you, and it is our top priority as soon as we wrap up some improvements to how we model app ownership in Apigee X/hybrid. If you see opportunities for how we might accelerate that by improving how community contributions get reviewed/accepted, please do offer suggestions (perhaps as a new issue or we could enable discussions for the project?). Note that in general, the bigger the PR and more files it touches, the more complicated the review will be. |
Hey @earth2marsh. |
How contributions are handled currently and what are the potential improvements in that regard is probably a side track here. Being g that said, please allow me to share my quick feedback on that: I also kept asking for reopening issues that Github Actions auto-closed because there were "no activity" on them. My personal opinion that such feature only works when there is capacity to actively check incoming issues and PRs on a project every day. Without a first response from a maintainer (which is not just an "ACK") no bot should auto-close issues. Also, instead of auto-closing them, first they should move the "stale" status. The Symfony project can be a good inspiration for configuring the bot.
|
In order to keep this issue focused on Drupal 10, I enabled Discussions and started a thread where we can discuss what the most effective way to manage maintainers vs contributors should be, and another discussion for suggestions on improving contribution workflows in the project. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hi, a couple months have passed here since the last comment...any chance we could get an update on the timeline for releasing a stable D10 version? Some of our customers have begun asking how long they will have for testing the D10 update - and even if Apigee releases a D10 version next week, that leaves 4 months before D9's EOL. That may seem like a lot, but we'll need to prepare, integrate, test, package and deliver before our customers can UAT and schedule deployments. That realistically leaves 2 months for UAT (which is already troubling for some customers) - and that number will quickly decrease over the coming weeks. |
Hi @janmashat , |
Hi All, We have released Drupal 10 compatible Apigee Edge module version 3.0.0. |
@divya-intelli Thanks for the announcement here! I see the new module is only compatible with D10 (not D9), which means it can't be tested out until the whole Drupal project moves to D10. Is that a conscience decision by Apigee, or maybe an oversight? If it's compatible with D9, it would be great to see it work with both 9 and 10 versions... |
Hi @dpagini , |
@dpagini , |
Is your feature request related to a problem? Please describe.
Release a module version that is compatible with Drupal 10.
Describe the solution you would like
Need to have this module ship a D10/PHP8.1 compatible version before we can update our site to Drupal 10.
Describe alternatives you have considered
Not using the Apigee suite of modules?
Additional context
N/A
The text was updated successfully, but these errors were encountered: