I thought since 3.20 all .0 versions are marked as "release candidate"
Stefanos On Fri, 16 Jan 2026 at 09:31, Régis Haubourg <[email protected]> wrote: > Well, my IT department updates packages in our software portal whenever > they ... want or users ask. > > Maybe we should explicitly name 4.0 "release candidate" in the package > names and our communication if 4.0 is that broken. > Regis > > > Le 16 janvier 2026 01:49:16 GMT+01:00, Nyall Dawson via QGIS-PSC < > [email protected]> a écrit : > >> >> >> On Thu, 15 Jan 2026 at 19:30, Andreas Neumann <[email protected]> >> wrote: >> > >> > Hi all, >> > >> > Regarding testing/bugfixing. >> > >> > 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. >> >> 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!) >> >> Nyall >> >> > >> > Andreas >> > >> > On 2026-01-15 08:01, Stefanos Natsis via QGIS-PSC wrote: >> > >> > 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. >> > >> > Best >> > Stefanos >> > >> > >> > On Thu, 15 Jan 2026 at 08:37, Nyall Dawson via QGIS-Developer < >> [email protected]> wrote: >> > >> > On Thu, 15 Jan 2026 at 16:00, Andreas Neumann <[email protected]> wrote: >> > > >> > > +1 - to have a voice from PSC ;-) >> > >> > Perfect, thanks Andreas! >> > >> > Nyall >> > >> > > >> > > Andreas >> > > >> > > >> > > >> > > On Thu, 15 Jan 2026 at 03:50, Nyall Dawson via QGIS-Developer < >> [email protected]> wrote: >> > >> >> > >> On Wed, 14 Jan 2026 at 01:23, Martin Dobias <[email protected]> >> wrote: >> > >> > >> > >> > Hi all >> > >> > >> > >> > On Thu, Jan 8, 2026 at 10:21 PM Nyall Dawson via QGIS-PSC < >> [email protected]> wrote: >> > >> >> >> > >> >> >> > >> >> I'm wondering if we could possibly push back the feature freeze >> date >> > >> >> by 1-1.5 weeks for this cycle? >> > >> >> >> > >> > >> > >> > +1 from me. >> > >> >> > >> So do we consider this locked in now? Freeze moved to 27th Jan? >> > >> >> > >> Nyall >> > >> _______________________________________________ >> > >> QGIS-Developer mailing list >> > >> [email protected] >> > >> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer >> > >> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer >> > > >> > > >> > > >> > > -- >> > > >> > > -- >> > > Andreas Neumann >> > > QGIS.ORG board member (treasurer) >> > _______________________________________________ >> > QGIS-Developer mailing list >> > [email protected] >> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer >> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer >> > >> > >> > _______________________________________________ >> > QGIS-PSC mailing list >> > [email protected] >> > https://lists.osgeo.org/mailman/listinfo/qgis-psc >> > >> > >> >
_______________________________________________ QGIS-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
