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

Magento upgrades best practices #32862

Open
mmansoor-magento opened this issue Apr 26, 2021 · 5 comments
Open

Magento upgrades best practices #32862

mmansoor-magento opened this issue Apr 26, 2021 · 5 comments
Labels
Adobe Summit Hackathon Area: Other Developer Tools Issue: ready for confirmation Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Progress: ready for dev R&D

Comments

@mmansoor-magento
Copy link
Contributor

The goal of this R&D task is to create guidance on Magento upgrades and publish it to devdocs.

Topics to discuss

  • Evaluation/estimation of Magento upgrades
  • Preparation for the upgrade
  • Upgrade process
  • Tips and tricks

Internal tickets:
MC-41324
MC-41190

@m2-assistant
Copy link

m2-assistant bot commented Apr 26, 2021

Hi @mmansoor-magento. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

  • Summary of the issue
  • Information on your environment
  • Steps to reproduce
  • Expected and actual results

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:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this


⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 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

@sidolov sidolov added the Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. label Apr 26, 2021
@shikhamis11
Copy link
Member

Along with the steps added in the dev doc for upgrade
I would like to mention some know issues related to Magento upgrades which can be found here
https://support.magento.com/hc/en-us/sections/360003869892-Known-issues-patches-attached-
also on the release note page of every version
for Example : https://devdocs.magento.com/guides/v2.4/release-notes/open-source-2-4-2.html#known-issues

I have experienced Images related issues while upgrade from Magento 2.2.x version to 2.3 or 2.4
#19710

@hostep
Copy link
Contributor

hostep commented Apr 26, 2021

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.

@sgonzalezmangana
Copy link

sgonzalezmangana commented May 12, 2021

Hi,
I'm Sandra Gonzalez, product manager at Adobe Commerce.
Perfect time for this issue, we are working on an "Upgrade Best Practices Guide" planned to be added on devdocs, your contributions would be more than welcome.
We are also planning to have an upgrade guide to move from 2.3.x to 2.4.x please let me know if you would like to work on it or collaborate.

@keharper
Copy link
Contributor

@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.

magento/devdocs#9010

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Adobe Summit Hackathon Area: Other Developer Tools Issue: ready for confirmation Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Progress: ready for dev R&D
Projects
None yet
Development

No branches or pull requests

7 participants