<div dir="ltr">I really like this suggestion. This would let users test version 4.2 early and they could keep their own roadmap. They can even go live with it already and get updates for a long time. And we can still call the LTR stable when it is ready.</div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Tue, Sep 1, 2026 at 3:05 PM Stefanos Natsis via QGIS-Developer <<a href="mailto:qgis-developer@lists.osgeo.org">qgis-developer@lists.osgeo.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>We could still have 4.2 as LTR, just aim for a (much) later release, like 4.2.8 or even later</div><div>During these 6 (or more) months we can promote fixing 4.0/4.2 bugs/regressions instead of (or in addition to) the paid bugfixing rounds.</div><div>As usual, big part of the problem are the unreported bugs though...</div><div><br></div><div>Best,</div><div>Stefanos</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 1 Sept 2026 at 15:45, Denis Rouzaud via QGIS-Developer <<a href="mailto:qgis-developer@lists.osgeo.org" target="_blank">qgis-developer@lists.osgeo.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Indeed, I misread Nyall's email. My personal take here would be that we extend the next feature freeze to the required period to get the stability required instead of adding new features.<div><br></div><div>But in any case, the roadmap needs to be updated as soon as possible as it still presents 4.2 as next LTR.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le mar. 1 sept. 2026 à 14:39, Jürgen E. Fischer via QGIS-Developer <<a href="mailto:qgis-developer@lists.osgeo.org" target="_blank">qgis-developer@lists.osgeo.org</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
On Tue, 25. Aug 2026 at 10:26:09 +1000, Nyall Dawson wrote:<br>
> On Mon, 24. Aug 2026 at 15:14:57 +0200, Jürgen E. Fischer wrote:<br>
> > On Fri, 21. Aug 2026 at 11:54:28 +1000, Nyall Dawson via QGIS-Developer wrote:<br>
> > > I don't think we're there yet for 4.2. 3.44 is a VERY solid release,<br>
> > > and I think we'd be doing our enterprise users a disservice by<br>
> > > officially promoting the idea that 4.4 is just as stable.<br>
> ><br>
> > So your suggestion is to removed the ltr-4_2 tag and continue 3.44 as LTR for<br>
> > the forseeable future until there is a 4.x release that is close to the<br>
> > stability of 3.44?<br>
> <br>
> That's my feeling.<br>
<br>
> (I mean -- try opening a layout, selecting two items, and group ...<br>
> *CRASH*. This is the kind of fundamental issue I'm referring to when I<br>
> say 4.2 isn't a match for 3.44 for stability).<br>
<br>
On Tue, 01. Sep 2026 at 14:30:46 +0200, Denis Rouzaud wrote:<br>
> It looks like there is an agreement of having 4.4.x as the next LTR.<br>
> If so, can we adapt the roadmap <a href="https://qgis.org/resources/roadmap/" rel="noreferrer" target="_blank">https://qgis.org/resources/roadmap/</a><br>
> So we can communicate (since LTR is supposed to happen in 3 weeks!)<br>
<br>
It's not what Nyall suggested.<br>
<br>
<br>
Jürgen<br>
<br>
-- <br>
Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31<br>
Dipl.-Inf. (FH) <a href="https://www.google.com/maps/search/Rheinstra%C3%9Fe+13?entry=gmail&source=g">Rheinstraße 13</a> Fax. +49-4931-918175-50<br>
Software Engineer D-26506 Norden <a href="https://www.norbit.de" rel="noreferrer" target="_blank">https://www.norbit.de</a><br>
QGIS release manager (PSC) Germany Matrix: @jef:<a href="http://osgeo.org" rel="noreferrer" target="_blank">osgeo.org</a><br>
_______________________________________________<br>
QGIS-Developer mailing list<br>
<a href="mailto:QGIS-Developer@lists.osgeo.org" target="_blank">QGIS-Developer@lists.osgeo.org</a><br>
List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
</blockquote></div>
_______________________________________________<br>
QGIS-Developer mailing list<br>
<a href="mailto:QGIS-Developer@lists.osgeo.org" target="_blank">QGIS-Developer@lists.osgeo.org</a><br>
List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
</blockquote></div>
_______________________________________________<br>
QGIS-Developer mailing list<br>
<a href="mailto:QGIS-Developer@lists.osgeo.org" target="_blank">QGIS-Developer@lists.osgeo.org</a><br>
List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
</blockquote></div>