The discussion of update checking got me thinking... When Picard v3.0 is released, are we planning to still potentially issue bug fix point releases to the 2.12 version? If so, the current update checker won't be of any use for notifying v2.12 users of point updates because it will always say that the latest version is v3.x. One way around this would be to introduce another setting to check the current major
version only, but this would also require that the update check manifest from the server provide the latest updates for both (all?) major versions. Any thoughts on how we should handle this, or if we should just leave the update checking system as-is (considering v2 will likely have a limited life once V3 is released because it's really only there to accommodate systems like Windows 7 that don't support Qt6)?
outsidecontext[m
Bob Swift: We might do so, but only to a limited degree. Target would be users of old OS or Linux distros that don't update to a new major version. But not sure we need the minor version check only.
