View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011855 | MMW v4 | Install/Config | public | 2014-02-12 16:51 | 2019-04-05 20:41 |
| Reporter | lowlander | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 4.1 | ||||
| Target Version | 5.0.0 | Fixed in Version | 4.1.23 | ||
| Summary | 0011855: Update checker doesn't work for beta builds | ||||
| Description | Currently user can enable to check for Updates, but this only checks for final releases. There should be an additional option to advise on new beta releases. This helps both users in staying informed as well as developers with limiting the amount of bug reports on old beta releases. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1881 | ||||
|
|
I would suggest that no UI is required. i.e. if a user is running a beta build, then the update notification should notify the user of the latest beta update. This will have the added improvement that currently, beta users don't get notified when a new Release_build is released. e.g. if a user is testing 4.1.0.1690, and then the final release build of 4.1.0.1692 is posted (including the new versions.xml file), then the user isn't even notified of that release--when they do an update check, they're told that 4.1.0.1690 is the most recent build (because versions.xml doesn't include build numbers)!! |
|
|
It isn't needed for those on a beta build, but the proposed UI would be useful in the sense that it would inform those willing to beta test and on a regular build that a new round of beta testing has begun. |
|
|
It seems that users who use a beta don't get notified on final release. So using 4.1.1.1700 won't notify on 4.1.1.1703 being released. |
|
|
This has been already fixed in 4.1.23.1881 in course of 0015153 |
