Feature proposal #7837
closed
Allow stable CB version check against build release
Added by krileon over 4 years ago.
Updated about 4 years ago.
Start date:
04 February 2020
Description
Currently if you install a stable CB release it will not check against build releases. Implement a parameter to toggle whether you want this behavior and by default always check against build releases. Users are constantly getting behind on releases and reporting issues that have already been fixed so this behavior is a negative user experience.
The real problem is imho different: We don't have regulare stable maintenance releases. Maybe we should have monthly CB releases, so that would be less critical.
The real problem is that if you decide to go nightlies, and then there is a stable, you get stuck on stables. Which in most cases is the wanted behavior. So not sure if we w
Most people don't want to upgrade daily. And if there is a security release, it's always in a stable one anyway.
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
You can already disable checking for build releases by turning off plugin version checking. There's no reason for us to enforce stable vs stable strict version checking internally when they can optionally have that themselves if they so choose. Currently core CB is removing that choice for them. If you update from a build release to a stable release you've just lost your option of build release version checking and have to go to manually checking the version in install from web or through our site. This is just bad user experience. It should be a users choice via turning off plugin version checking or consider a separate parameter for it.
Implemented in MR !1527
We don't release CB builds on a daily basis so I don't think that's a critical issue, but even so they can just disable plugin version checking and it will only check for stable releases. Even releasing monthly won't solve the problem of people posting about bugs we've already fixed, which is exhausting more time than fixing the bug they're posting about.
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by 
Updated by