Description: Using the 7.2.7 version (confirmed version), the system is suggesting to download the new 7.3.4 version (technology enthusiast) Remark: Using a French version, I may not mention the exact terms of the English version. Actual Results: System suggesting update 7.3.4 Expected Results: No new update should be suggested as version 7.2.7.2 is already installed. Reproducible: Always User Profile Reset: No Additional Info: -
Created attachment 181101 [details] screenshot
The 7.2.7 release went EOL 22 June. Remain on it if you prefer. 7.3.4 is the appropriate update on the Still branch as 7.4.0 enters release and is the correct offering at this time.
I am not stupid! Something is wrong. On your site, version 7.3.4 is for “technology enthusiasts” and version 7.2.7.2 for “business deployments” and users who are not “technology enthusiasts” (what you call “Still branch”?). Version 7.3.4 should not be suggested to them, unless your site is not up to date! Please be consistent!
Please see the linked release plan. The cut over from previous release to current release is time based. It is time for the cut over to be noted via the "update checks"--yes offering 7.3.4 now might be a couple of weeks early (7.4.0 will be out mid-August) but in sum this is appropriate as 7.2.7 *is* EOL. And yes, the landing page for the downloads still reflects 7.2.7 as Still and 7.3.4 as Fresh--that will be updated as 7.4.0 is released. For now updates are not automatic--just the notification that update is available. You still have complete control as to performing an update--or not.
Hi Stuart, Thank you for your explanation. My wife has got problems in the past updating too early to the « fresh » version. Nevertheless, the whole process is not very consistent for a normal user... Have a good day! Luc
*** Bug 150156 has been marked as a duplicate of this bug. ***
*** Bug 150050 has been marked as a duplicate of this bug. ***
*** Bug 149774 has been marked as a duplicate of this bug. ***
*** Bug 161432 has been marked as a duplicate of this bug. ***
*** Bug 161807 has been marked as a duplicate of this bug. ***