[QGIS-Developer] [Qgis-psc] QGIS LTR releases -- is it time to pull the plug?

[C Hamilton]

+1 you concisely expressed my thoughts about this.

Calvin

On Wed, Nov 17, 2021 at 1:45 PM Bo Victor Thomsen <
bo.victor.thomsen at gmail.com> wrote:

> Hi list -
>
> I've summed up some ideas about have to handle the LTR situation.  The
> policies is not carved in stone or complete but suggestions for a more
> stable regime regarding LTR  (and they have probably already been mentioned
> sometimes by someones before)
>
> However - Policy for LTR releases:
>
>    - At most one LTR release for every year.
>
>    - Point releases for LTR every 2 or 3 months.
>
>    - Point releases for LTR contains only security or bug patches. Never
>    introduce new functionality or change in the user interface ( Translation
>    files might be exempted from this rule)
>
>    - The supporting libraries ( qt, proj, gdal, ogr etc. ) is covered by
>    the same rules. Only security or bug patches, never introduce newer major
>    versions.
>
>    - Major changes in supporting libraries for non-LTR releases is
>    restricted to the release just after a LTR. Thus there will be 3 or more
>    non-LTR releases to stabilize QGIS before next LTR.
>
>
> The general idea is that the QGIS release following a LTR is a "Big Bang"
> release: Everything goes.
>
> The following non-LTR releases can introduce new functionality but no
> changes in the supporting libraries (This rule could maybe be bend a
> little) . But when you come around to the LTR release you deep-freeze any
> changes except security- and bug correcting patches
>
>
> Med venlig hilsen / Kind regards
>
> Bo Victor Thomsen
>
> Den 17-11-2021 kl. 08:27 skrev Luca Manganelli:
>
> > [... ]
>
> As an IT administrator in our public organization, I confess that I have
> packaged and distributed to all PCs the (old) 3.16.4 version. Why? Because
> with this version there are 0 problems among users and with our customized
> plugins.
>
> Before the 3.16 release, the other 3.x versions were a disaster, many
> things didn't work, so before this 3.16, I had distributed 2.x to many
> users and 3.12 to only few PCs.
>
> In a big organization the most important thing is not, "strangely", the
> more features a piece of a software has, but the ... stability. Remember
> that every worker wants a product that... works.
>
> And, the upgrade. The QGIS package is big (the archive is over 320MB) and
> we have many offices in sloooow networks (2M ADSL... don't laugh, this is
> the situ
>
>
>
>
>
>
>
>
>
> ------------------------------
>
> Comune di Trento
>
> via Belenzani, 19 - 38122 Trento | C.F e P. IVA: 00355870221
>
> tel. +39 0461.884111 | www.comune.trento.it
>
> _______________________________________________
> QGIS-Developer mailing listQGIS-Developer at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
> _______________________________________________
> QGIS-Developer mailing list
> QGIS-Developer at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20211117/ddd3072e/attachment-0001.html>