-
Notifications
You must be signed in to change notification settings - Fork 118
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
Maintenance: EA Inspections team, solve compatibility issues and follow contractual obligations #1882
Comments
@kalessil Locally I've fixed usage of all deprecated APIs a couple of months ago (just to better understand changes in the Intellij API), and I could share changes (privately or as a public PR):
|
Thanks, @dryabov! Sharing in public, as a diff file(s), or embedded into a comment for this ticket, will work great! |
@ea-inspections-team, thanks for getting in touch with an email, but this escalation has to go thru the public channel:
Please explain what happens and the options to resolve the current situation. |
glad to see this is finally getting some love. |
Hi @kalessil, Current situation is that since April of last year we don't have people who could work on this project. Not much I can do, only to use the fixes from @dryabov and to release the compatibility fixes on next week. Sorry that this turned this way, I'm finding out the agreement details only last days. |
@ea-inspections-team, thank you for responding here. To move forward:
Deliverables and expectations:
PS: As I'm not the person who signed the contract nor is responsible for finances, I've asked the person to initiate the handover. |
@ea-inspections-team: to clarify, I'm aiming to get the project back to feet and open to future cooperation once things improve on your end. |
Just in case, I would like to draw your attention to a few points:
Good luck! |
We are after deadline, still no fix :( |
@kalessil: previous maintainers shared with us the most of credentials (except gmail, perhaps you have original ones somewhere?) The expectations can not be fulfilled: we received credentials yesterday, but it was no communication about your expectations. We assuming the priorities didn't change and highest is compatibility releases, can you confirm? |
@ea-inspections-team, gosh, that turned ugly. Please ASAP release compatibility fixes - it's an absolute priority. Even if it takes 2-3x monthly time - we can revisit the time allocation later, but make it happen. |
There is now a build for "PhpStorm 2023.1.x": https://github.com/Haehnchen/phpinspectionsea/releases see PR with changes to get it working based on @dryabov changes #1883 |
@ea-inspections-team When will the new EA Ultimate version be available? |
@kaliberx, given 2-3 business day for approval by JetBrains administrators, it should be available next Tuesday/Wednesday. |
@kalessil, the timeline as you requested:
We don't anticipate further delays, and provide post-release monitoring over next week. |
Thank you, @ea-inspections-team! Please ensure to post updates in this thread when uploading new builds and when those get approved, thank you. |
@kalessil: Php Inspections (EA Extended) is uploaded (version 5.0.0.0) and awaits for approval. Please note following:
|
Great! Thank you @dryabov @Haehnchen @ea-inspections-team ! |
@kalessil: Php Inspections (EA Ultimate) is uploaded (version 2023.1) and awaits for approval. Please note:
|
@kalessil: Php Inspections (EA Extended) update was approved on Friday, we'll keep monitoring for new issues. Php Inspections (EA Ultimate) update was rejected due to similar compatibility issues as Extended, we'll re-upload it today. If the update is not rejected again, it should be released on Wednesday. |
@kalessil: we addressed points from the last rejection and uploading a new build. If it doesn't solve the compatibility issues, we are have to increase minimally supported version of IDE. |
@ea-inspections-team: thanks for keeping me in the loop. Please make sure that both plugins have the same supported versions of IDE. Also, the update page shows you compatibility verification results for each plugin, so you don't have to wait for admins' feedback - if struggling, ask for guidance from them. From my experience, they were always able to help out with pointers. |
@ea-inspections-team, can you please update me on your current status? |
@kalessil: yes. Thank you for your hints, we were able to build a new release, and QA discovered that settings in Php Inspections (EA Ultimate) are not working. My last update from Wednesday is that the issue is in work. I'll post a new update on Wednesday when returning back from a vacation. Probably engineers have everything ready already, and waiting for a confirmation to release. |
@ea-inspections-team: thank you for the details, much appreciated, and I hope everything is ready for release on Wednesday. As quick feedback:
|
To keep everyone in the loop: folks get stuck (components I introduced back then), and I'm guiding them as my capacity allows. |
@ea-inspections-team are you still struggling with the Ultimate code? Please share your progress and ETA. |
@kaliberx: nope, @ea-inspections-team is unblocked - we are syncing with them tomorrow on the release status. |
Hopefully, the last update here: there is "go" for release. I'll also be AFK next week, but I will verify release availability on Monday. |
Closing this one: the update is still marked as waiting for approval, but compatibility checks are passing. @ea-inspections-team: please share the roadmap for 2023, IIRC it should be 2 more releases for extended + 2 releases more for ultimate this year and I'm eager to see more bug-fixing. We all can support you with triaging if that helps to focus on development. |
I just installed the new EA Ultimate version. Thank you so much! <3 |
@ea-inspections-team: with all understanding of your situation, please address the compatibility issues ASAP!!!
My requests to get permission/emails/DMs are answered but @ea-inspections-team assured me things under control.
To say I'm frustrated is the least I can do, please sort things out as per your contractual obligations by end of this week!!!
The text was updated successfully, but these errors were encountered: