<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p>Hi,</p>
<p>I would label it "Release candidate" until 4.2 is released.</p>
<p>Andreas</p>
<p id="reply-intro">On 2026-01-16 08:31, Régis Haubourg wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<div id="replybody1">
<div dir="auto">Well, my IT department updates packages in our software portal whenever they ... want or users ask. <br /><br />Maybe we should explicitly name 4.0 "release candidate" in the package names and our communication if 4.0 is that broken. <br />Regis</div>
<br /><br />
<div class="v1gmail_quote">
<div dir="auto">Le 16 janvier 2026 01:49:16 GMT+01:00, Nyall Dawson via QGIS-PSC <qgis-psc@lists.osgeo.org> a écrit :</div>
<blockquote class="v1gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid #cccccc; padding-left: 1ex;">
<div dir="ltr"><br /><br />On Thu, 15 Jan 2026 at 19:30, Andreas Neumann <<a href="mailto:a.neumann@carto.net" rel="noreferrer">a.neumann@carto.net</a>> wrote:<br />><br />> Hi all,<br />><br />> Regarding testing/bugfixing.<br />><br />> I hope and I assume that companies and organizations wouldn't have the idea to base their mission critical work on a .0 release ... but rather wait for the next LT version or a couple of patch releases until QGIS 4.x can mature further.
<div> </div>
<div>Definitely -- it's not going to be anywhere NEAR enterprise ready 🤣. (I just ran into the known issue where the qt6 builds can corrupt your user profiles... someone should probably look into that one sometime!)</div>
<div> </div>
<div>Nyall</div>
<div><br />><br />> Andreas<br />><br />> On 2026-01-15 08:01, Stefanos Natsis via QGIS-PSC wrote:<br />><br />> I'm also +1, however I'm slightly worried that we should somehow compensate for the reduced testing/bugfixing time of this feature-rich release.<br />> <br />> Best<br />> Stefanos<br />> <br />><br />> On Thu, 15 Jan 2026 at 08:37, Nyall Dawson via QGIS-Developer <<a href="mailto:qgis-developer@lists.osgeo.org" rel="noreferrer">qgis-developer@lists.osgeo.org</a>> wrote:<br />><br />> On Thu, 15 Jan 2026 at 16:00, Andreas Neumann <<a href="mailto:andreas@qgis.org" rel="noreferrer">andreas@qgis.org</a>> wrote:<br />> ><br />> > +1 - to have a voice from PSC ;-)<br />><br />> Perfect, thanks Andreas!<br />><br />> Nyall<br />><br />> ><br />> > Andreas<br />> ><br />> ><br />> ><br />> > On Thu, 15 Jan 2026 at 03:50, Nyall Dawson via QGIS-Developer <<a href="mailto:qgis-developer@lists.osgeo.org" rel="noreferrer">qgis-developer@lists.osgeo.org</a>> wrote:<br />> >><br />> >> On Wed, 14 Jan 2026 at 01:23, Martin Dobias <<a href="mailto:wonder.sk@gmail.com" rel="noreferrer">wonder.sk@gmail.com</a>> wrote:<br />> >> ><br />> >> > Hi all<br />> >> ><br />> >> > On Thu, Jan 8, 2026 at 10:21 PM Nyall Dawson via QGIS-PSC <<a href="mailto:qgis-psc@lists.osgeo.org" rel="noreferrer">qgis-psc@lists.osgeo.org</a>> wrote:<br />> >> >><br />> >> >><br />> >> >> I'm wondering if we could possibly push back the feature freeze date<br />> >> >> by 1-1.5 weeks for this cycle?<br />> >> >><br />> >> ><br />> >> > +1 from me.<br />> >><br />> >> So do we consider this locked in now? Freeze moved to 27th Jan?<br />> >><br />> >> Nyall<br />> >> _______________________________________________<br />> >> QGIS-Developer mailing list<br />> >> <a href="mailto:QGIS-Developer@lists.osgeo.org" rel="noreferrer">QGIS-Developer@lists.osgeo.org</a><br />> >> List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank" rel="noopener noreferrer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br />> >> Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank" rel="noopener noreferrer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br />> ><br />> ><br />> ><br />> > --<br />> ><br />> > --<br />> > Andreas Neumann<br />> > <a href="http://QGIS.ORG" target="_blank" rel="noopener noreferrer">QGIS.ORG</a> board member (treasurer)<br />> _______________________________________________<br />> QGIS-Developer mailing list<br />> <a href="mailto:QGIS-Developer@lists.osgeo.org" rel="noreferrer">QGIS-Developer@lists.osgeo.org</a><br />> List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank" rel="noopener noreferrer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br />> Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank" rel="noopener noreferrer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br />><br />><br />> _______________________________________________<br />> QGIS-PSC mailing list<br />> <a href="mailto:QGIS-PSC@lists.osgeo.org" rel="noreferrer">QGIS-PSC@lists.osgeo.org</a><br />> <a href="https://lists.osgeo.org/mailman/listinfo/qgis-psc" target="_blank" rel="noopener noreferrer">https://lists.osgeo.org/mailman/listinfo/qgis-psc</a><br />><br />></div>
</div>
</blockquote>
</div>
</div>
</blockquote>
<p><br /></p>
</body></html>