Better update handling

Hello,

I would like to request RDM/DVLS update management improvement.

With the current system, we have some trouble. Let me explain:
As a current example, we had RDM .24 running. In the last couple of days I wanted to update to .35. So my idea was this:
Set required to .24, set max to .99.
Set recommended to .35.
Activate auto update.
Hope users will get information to upgrade.

However, after trying it out, I saw it doesn't work like that. Moreover, I was informed that it won't update, as long as I don't change that .24 minimum version and force users to upgrade. I can set recommended version, which will install that version instead of going to the latest, is my understanding.

The problem with this concept is that if I set it any time, users that are working, and there are also some that work after 5pm, will sooner or later get a popup, as soon as RDM attempts to connect to the DB. Which means, their work will potentially be interrupted - not optimal. Some systems have not updated for days, one of our colleagues got the prompt today, while I activated the update last week. He was maybe offline all the time, I don't know.

My suggestion to improve the concept:
When recommended version is set (and is higher than what the user is using), without changing the required version, user should get a notification to upgrade. Ideally, I could also be able to write a custom note, saying something in lines of "Update to this version at latest as soon as possible, it will be set to required in 7 days". Which would mean, user has a week to update, without disrupting his/her work and can click on cancel.
Also there should be an option to disable "Skip this version" in the menu. And the update should open each RDM startup, until the user updates.
It would basically mean nagging the user to update, without disrupting their work.
User should be able to click on Help -> Check for updates.

I think this would go a long way towards productivity improvement.

Thanks
Srdan