-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Magento upgrades best practices #32862
Comments
Hi @mmansoor-magento. Thank you for your report.
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
For more details, please, review the Magento Contributor Assistant documentation. Please, add a comment to assign the issue:
🕙 You can find the schedule on the Magento Community Calendar page. 📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket. 🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel ✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel |
Along with the steps added in the dev doc for upgrade I have experienced Images related issues while upgrade from Magento 2.2.x version to 2.3 or 2.4 |
For the tips & tricks part, the obvious tool to mention here is https://github.com/AmpersandHQ/ampersand-magento2-upgrade-patch-helper which I'm using for all Magento upgrades and is a very good and helpful tool in detecting certain customisations done to a shop that should be investigated after a Magento upgrade. |
Hi, |
@hostep @shikhamis11 and anyone else interested in this issue. I created the following PR and will it open for one week to incorporate community feedback. |
The goal of this R&D task is to create guidance on Magento upgrades and publish it to devdocs.
Topics to discuss
Internal tickets:
MC-41324
MC-41190
The text was updated successfully, but these errors were encountered: