On Fri, 5 Nov 2021 at 10:25, Jürgen E. Fischer <j...@norbit.de> wrote: > > Hi Nyall, > > On Fri, 05. Nov 2021 at 08:28:33 +1000, Nyall Dawson wrote: > > > We also then need to push out a news feed item advising that 3.16.12 > > > has critical issues and that all users should update to 3.16.13. > > > Any response to this? I feel SO strongly that we need to push this out > > as a matter of urgency. > > Hm, I don't. The affected windows packages are already fixed. People just > need to update to the latest packages. Doing another release wouldn't change > nothing more than the version number and trigger a lot of otherwise useless > rebuilds - even on platforms that were not even affected. And the next point > release is only two weeks away.
Mmm... I really don't think that works for end users though. Someone who has installed qgis 3.16.12 from last week's installer has no way of telling that they'll be affected by the bug vs someone who only just downloaded the installer. There's no way we can put out any announcement and say "check the about screen and if your version says .... then you need to update". This also gets SUPER messy for enterprise deployments, since users won't have any way at all of knowing which installer was actually used for their QGIS version. And for these enterprise deployments the actual staff doing the packaging are unlikely to be running QGIS themselves, so a notice on the news feed won't get their attention. Suffice to say, I think the only way forward is to kill 3.16.12 with fire and bump the version. Nyall _______________________________________________ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer