Bug report #15278
Long term release installer 2.14 installs 2.16 and makes 2.16 default version
|Affected QGIS version:||2.14.3||Regression?:||No|
|Operating System:||Windows||Easy fix?:||No|
|Pull Request or Patch supplied:||No||Resolution:||fixed/implemented|
|Crashes QGIS or corrupts data:||No||Copied to github as #:||23213|
I find this very harmful. QGIS long term installer of version 2.14.4-1 installs also version 2.16 and makes 2.16 default version. QGIS users who are not that found of versioning easily open and save projects in 2.16 which makes it not fully backward compatible with version 2.14 = corrupting projects.
#2 Updated by Miroslav Umlauf about 4 years ago
Sorry for not stating this right at the beginning.
#4 Updated by Andre Joost about 4 years ago
- Target version changed from Version 2.14 to Version 2.16
Unfortunately, the standalone Windows version lacks the python future lib. QGIS 2.14.4 does not need it, but QGIS 2.16 does. As a consequence, 2.16 has Python disabled. See also https://trac.osgeo.org/osgeo4w/ticket/514 and http://gis.stackexchange.com/questions/202092/python-error-when-loading-qgis-on-windows-10
I suggest to drop QGIS 2.16 from the 2.14.4 installer completely.
#5 Updated by Miroslav Umlauf about 4 years ago
- Target version changed from Version 2.16 to Version 2.14
I completely agree. I do not like that there is version 2.16 in installation of long term release and especially as default version. I believe the idea of long term release is to have long term release, not to use 2.16, after few months 2.18 etc.
Target version should stay 2.14 (this long term release). I don't like the idea that for another year I will have to explain to everyone that with installation of long term release 2.14 they will actually switch to 2.16 and not to 2.14. Suggesting some workarounds how to make 2.14 default as it should be default and always be afraid that someone unintentionally use 2.16 which will CORRUPT workspaces for 2.14 users.