Open adarshkhatri opened 1 year ago
Hi @adarshkhatri. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:
@magento give me 2.4-develop instance
- upcoming 2.4.x release@magento I am working on this
Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.
~Maybe @sidolov know?~
Hi @adarshkhatri, I see the file you referenced in 2.4.6-p2 was changed 2 years ago, while in 2.4-develop - only 9 months ago. If we compare the history - in 2.4-develop we have the following commit https://github.com/magento/magento2/commit/b4208512bce542afc8b5b0bf3a9a551a5905ee8e, while it wasn't included yet in 2.4.6-p2. Instead, it's available as a part of 2.4.7-beta1. So it feels like the file is in sync. If you have any other examples, let's review them.
Is there any doc around when the latest develop
will be used to create the new release?
This is not a bug but a Question (*)
I am comparing
2.4-develop
V/S2.4.6-p2
and can see a lot of differences. For example these:My understanding was new versions are created from
*-develop
version as we always test the bug against it. At what point of time version2.4.6-p2
will be merged to2.4-develop
?