<div dir="ltr"><div dir="ltr">Hello Jürgen,<div><br class="gmail-Apple-interchange-newline">If I get it right, even if the 4.4.x branch was created today (including the LTR blocking issues), that would just feed the regular repos until march 2027, so not worse than today since 4.2 also has these issues. Then there would still be until march 2027 to fix these blocking issues and backport them to the branch so that they don't land in the LTR repos, no ? (sorry if I'm confused, here we're just discussing which version we target to roll out to our users, so I'd be happy to fully understand this :-) )</div><div><br class="gmail-Apple-interchange-newline">For the time frame, my question was about an estimate for the delay for 4.4.0 as LR (either with blocking issues fixed or reclassified). And if we can already foresee some delays for 4.4.4 as LTR, of course that would be great to know too (for instance if 4.4.0 ends up significantly delayed, would we also postpone the LTR so that it gets enough time to mature ?).</div><div><br></div><div>Cheers !</div><div><br></div><div>Olivier</div><div><br></div><div><br></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Fri, 6 Nov 2026 at 11:52, Jürgen E. Fischer 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">Hi Olivier,<br>
<br>
On Fri, 06. Nov 2026 at 11:05:36 +0100, Olivier Dalang via QGIS-Developer wrote:<br>
> Just a quick question for my understanding: from the published roadmap, I<br>
> thought that 4.4 was meant to replace 3.44 as the LTR only in march 2027,<br>
> and that before that, 4.4 was just a regular release. If so, wouldn't it be<br>
> enough to sort out those issues by then, so that latest release users can<br>
> already adopt 4.4 ?<br>
<br>
The branch is what gets long-time care and therefore it gets the ltr tag when<br>
it's branched off.<br>
<br>
That it doesn't replace the old LTR in the package repositories right away is<br>
just a technicallity. We build two branches - one feeds the LTR repos and one<br>
the regular repos - and while the new LTR is also the latest release it still<br>
feeds the regular repos, while the previous still feeds the LTR repos.<br>
<br>
As side effect it get some more time to mature as people can try the new LTR<br>
release, while the old LTR is still available (and even being maintained).<br>
<br>
> Also it would be great to have an idea (even if very vague) about how much<br>
> delay we're talking about, to help making deployment plans in this tricky<br>
> 3->4 transition time. Are talking about a few more days or could it be<br>
> months ?<br>
<br>
You mean how long it will take to fix or reclassify the blocking issues?<br>
<br>
<br>
Jürgen<br>
<br>
-- <br>
Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31<br>
Dipl.-Inf. (FH) Rheinstraße 13 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></div>