Repository navigation
Handling a sequence of mixed mandatory status updates #253
Description
If I have a new release (let us say 1.0.0.1) that I wish to make mandatory, I understand I can simply set the <mandatory> flag true. If I later have another release (1.0.0.2) which is not mandatory, I would then set the <mandatory> flag false. However, if a user does not run the program between version 1.0.0.0 and 1.0.0.2, won't they miss the mandatory update? Is there a way to avoid this happening?
Activity
RGerrish commentedon Mar 28, 2019
This might just be me messing something up, but I haven't been able to get it to look past the 1st entry in the xml file.
Henri77 commentedon Mar 28, 2019
I assumed that only one entry was expected in the XML file. That was the reason for my question.
RGerrish commentedon Mar 28, 2019
Glad I'm not the only one that would love to see multiple entries then :-)
Henri77 commentedon Mar 28, 2019
Here are my thoughts, for what they are worth.
Although multiple entries would allow the full release history to be assessed for update purposes, as the history got longer so the time to read the file would increase.
I think only two XML file entries would be required - one for the most recent mandatory version and one for the most recent optional version. If the running (current) version is less recent than the mandatory version this should force an update, even if the latest version is optional. Otherwise the optional update check would work as it does now.
Henri77 commentedon Apr 10, 2019
I see this is now marked as an enhancement/feature request. Could you please give me an indication of when/if it might be scheduled?