Hi Paolo
> On 23 Nov 2019, at 08:05, Paolo Cavallini <cavall...@faunalia.it> wrote: > > Hi all, > > Il 22/11/19 23:20, Even Rouault ha scritto: > >> Or one might consider a mixed approach to have a good compromise of agility >> vs >> tighter control: >> - use time-based approach, as done currently, for non-LTR versions. >> - formally approve the release of LTR versions, and important engineering >> decisions that affect them, as there are the ones with the most user >> exposure. >> Sometime ago I also suggested to possibly consider 2 phases in a LTR life- >> cycle: first half where quite "aggressive" backporting is accepted (if it >> doesn't break API, etc..), second half where a much more conservative >> approach >> is taken. It is rather obvious that a .0, .1 needs more stabilization than a >> . >> 12 or a .13 >> >> Just food for thought :-) >> >> Even >> >> (*) even bugfix ones, which is admidetly sometimes a bit overkill >> > > Thanks everybody for the analysis and the proposals. > IMHO the LTR should be as stable as possible, so I agree that changing > things now it's unfortunate. > An alternative is to freeze it, and don't release further updates. Are > there important bugfixes preventing us to do so? If I understand the situation properly, it is not possible to do this in the OSGEO4W framework (and maybe similar issue in Debian etc) since in OSGEO4W online installer there is only one proj, GDAL etc published and you cannot have e.g. QGIS 3.4.x depending on project 5 and QGIS 3.10.x depending on Proj 6 both both within the same OSGEO4W package tree. I think similar issue arises in Debian. I may be totally misreading the situation (I am sure Jürgen will correct me if I am :-) ).In the OSGEO4W side we would basically need to ask / fund Jürgen to support different packages for different versions of QGIS which I suspect may be a major pain in the butt. For windows at least we could ‘freeze’ 3.4.x by pointing them to use the standalone installers but then we have an LTR that is not getting bug fixes. As I read Jürgen’s roadmap [1] we still have 4 more bug fix releases of 3.4 before 3.10 becomes LTR, which is quite a long time to have our ’stable’ version out there with no bug fixes. PR 3.10.1 3.4.14 2019-11-29 48 3 PR 3.10.2 3.4.15 2019-12-20 51 4 PR/FF 3.10.3 3.4.16 3.11 2020-01-17 3 5 LR/PR 3.12.0 3.10.4 2020-02-21 8 4 Regards Tim [1] https://www.qgis.org/en/site/getinvolved/development/roadmap.html <https://www.qgis.org/en/site/getinvolved/development/roadmap.html> > Cheers. > -- > Paolo Cavallini - www.faunalia.eu > QGIS.ORG Chair: > http://planet.qgis.org/planet/user/28/tag/qgis%20board/ > _______________________________________________ > 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 — Tim Sutton Co-founder: Kartoza Ex Project chair: QGIS.org Visit http://kartoza.com <http://kartoza.com/> to find out about open source: Desktop GIS programming services Geospatial web development GIS Training Consulting Services Skype: timlinux IRC: timlinux on #qgis at freenode.net I'd love to connect. Here's my calendar link <https://calendly.com/timlinux> to make finding time easy.
_______________________________________________ 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
