[QGIS-Developer] Status of 3.44 becoming LTR?

Wed Sep 9 09:08:53 PDT 2026

Hi

On Wed, Sep 9, 2026 at 10:34 AM Stefanos Natsis <uclaros at gmail.com> wrote:

> Hi Tim,
>
> Thanks for the heads up!
>
> It is not clear to me which version will become the next LTR after 3.44.15
> according to the suggested plan. Is it 3.44.16? 4.4.4? Other?
>

Juergen posted an update to the roadmap here which I believe should clarify
it for everyone.
https://github.com/qgis/QGIS-Website/commit/c04e682d33add7084f49c35d5910f5cac592583c
- so it would be 4.4.4 according the schedule.

>
> One other thing that worries me a little is that the plan considers that
> the 4 "stability issues" are already reported, which I am not sure to what
> extent is the case.
>
>
I think the best way we can address this is for me to put out something in
the news feed / blog etc. announcing the change of plans and then to call
on people to test 4.x and report critical issues asap. But yes that is an
intractable problem that I think has no perfect solution.

Regards

Tim

> Best,
> Stefanos
>
> On Wed, Sep 9, 2026, 11:57 AM Tim Sutton via QGIS-Developer <
> qgis-developer at lists.osgeo.org> wrote:
>
>> Hi all
>>
>> Last night the PSC met and discussed this (and thanks to Denis for
>> joining us to discuss).
>>
>> We will share the full PSC meeting notes, but with regards to the LTR we
>> propose to follow the following steps:
>>
>>    - Create a new *LTR 4.x Blocker* tag for issues
>>    - Ask developers, Giovanni Manghi, Andrea Giudiceandrea to tag any
>>    breaking features with the new blocker tag so we have a clear sense of what
>>    needs to be done
>>    - Keep feature freeze until all blockers are gone.
>>    - *Stick to current schedule but QGIS 4.2 will no longer be LTR*
>>    - QGIS 4.4 to have a 6 week paid bug fixing period instead of 4 (and
>>    retain 6 week feature freeze)
>>    - Disable broken features if needed and communicate the feature
>>    regressions as part of the changelog
>>    - If there are still remaining blockers that we cannot simply disable
>>    at the end of the 6 weeks we will extend the release (last resort option)
>>
>>
>> Does this sound good for everyone?
>>
>> Regards
>>
>> Tim
>>
>> On Tue, Sep 1, 2026 at 1:31 PM Denis Rouzaud via QGIS-Developer <
>> qgis-developer at lists.osgeo.org> wrote:
>>
>>> Hi,
>>>
>>> It looks like there is an agreement of having 4.4.x as the next LTR.
>>> If so, can we adapt the roadmap https://qgis.org/resources/roadmap/
>>> So we can communicate (since LTR is supposed to happen in 3 weeks!)
>>>
>>> Cheers,
>>> Denis
>>>
>>> Le mar. 4 nov. 2025 à 18:51, Jürgen E. Fischer via QGIS-Developer <
>>> qgis-developer at lists.osgeo.org> a écrit :
>>>
>>>> Hi Greg,
>>>>
>>>> On Tue, 04. Nov 2025 at 08:59:06 -0500, Greg Troxel via QGIS-Developer
>>>> wrote:
>>>> > Yes, that makes sense and I understood the general plan.  What I was
>>>> not
>>>> > clear about was whether, today, 3.44 *was* the LTR or just *is going
>>>> to
>>>> > be*.  But from reading the roadmap, I convinced myself that today,
>>>> 3.40
>>>> > is LTR, and in late February, 3.44 will become LTR.  Confusingly, 3.44
>>>> > proclaims itself LTR in the splash screen, and it sort of is, kind of
>>>> > like crown prince.
>>>>
>>>> Well, in my view the ltr is a branch that is longer maintained as
>>>> others.  So
>>>> an ltr starts when it's branched off.
>>>>
>>>> We just build packages for the latest and long-term release and as that
>>>> wouldn't make much sense while both are the same, we continue to build
>>>> the
>>>> previous ltr, while the new ltr is also the latest release.
>>>>
>>>> That way we still have two lines to build and the new ltr has some more
>>>> time to
>>>> replace the previous.  That happens when the next version is released
>>>> and takes
>>>> its place as lastest release.
>>>>
>>>> That should also be the point were the splash is changed - which is
>>>> usually
>>>> with .4.  That would have been - but should have happend with .8 on this
>>>> branch.  The splash change was meanwhile reverted.  But I didn't bother
>>>> to
>>>> retag or do another point release just for this IMHO minor issue - the
>>>> branch
>>>> is a LTR branch.
>>>>
>>>>
>>>> Jürgen
>>>>
>>>> --
>>>> Jürgen E. Fischer           norBIT GmbH             Tel.
>>>> +49-4931-918175-31
>>>> Dipl.-Inf. (FH)             Rhe
>>>> <https://www.google.com/maps/search/Rhe?entry=gmail&source=g>instraße
>>>> 13          Fax. +49-4931-918175-50
>>>> Software Engineer           D-26506 Norden
>>>> https://www.norbit.de
>>>> QGIS release manager (PSC)  Germany                 IRC: jef on
>>>> Libera|OFTC
>>>> _______________________________________________
>>>> 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
>>>>
>>> _______________________________________________
>>> 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
>>>
>>
>>
>> --
>>
>>
>>
>> *Tim Sutton*
>> QGIS Project Steering Committee
>> tim at qgis.org
>> _______________________________________________
>> 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
>>
>

-- 

*Tim Sutton*
QGIS Project Steering Committee
tim at qgis.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20260909/4b048c31/attachment.htm>