Magento 2.4.0 release notification not showing up in backend

[hostep]

Preconditions (*)

1. Magento 2.4.0 or 2.4.1 or 2.4.2 or 2.4.3 or 2.4.4 or 2.4.5 or 2.4.6 or 2.4.7 or ...

Steps to reproduce (*)

1. Setup clean 2.4.0 or 2.4.1 or 2.4.2, ... installation, not a 2.4-develop instance! (see reasoning below)
2. Login to backend (struggle your way through the whole 2FA process rigmarole)
3. Once finally logged in, seeing a notification at the bottom of the page:

We’ll try to show it again the next time you sign in to Magento Admin.
To learn more about new features, see our latest Release Notes in DevDocs' Release Information

4. Also notice the strange 'Next >' link in the footer
5. Logout in backend
6. Login to backend
7. Not seeing any release notifications popup

Expected result (*)

1. Not being confused: if there are release notes for 2.4.0, show them, if there aren't, don't show that We’ll try to show it again ... message

Actual result (*)

1. Being confused: is there a release notes popup for Magento 2.4.0? If yes, why isn't it showing up? If no, why is that message We’ll try to show it again ... showing up ...

Additional information

#29363 (comment)

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

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

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ 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

[m2-assistant]

Hi @engcom-Oscar. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Oscar]

Hello @hostep

Thank you for your report.
Unfortunately, I was not able to reproduce this issue on the latest 2.4 code. Probably it was already fixed and will appear in the next release. Or we missed some steps or preconditions.

Could you please recheck and confirm?

[hostep]

@engcom-Oscar: I'm not sure, I think this release notification window should only pop up in fixed release versions as it is supposed to announce new big features in a new version. I don't think I ever saw it in development versions, so it can't be checked on 2.4-develop I believe, only on 2.4.0 or 2.4.1 (which should already be available as a beta, but I don't have access to the beta versions).

Can you maybe check internally with the architecture team how this thing is supposed to work and why it has this confusing behavior in 2.4.0?