Hi, Le ven. 24 janv. 2020 à 16:57, Mathieu Pellerin <[email protected]> a écrit :
> It's wise of you not to have your department jump on a .0 release. All > known (ie reported through filing) protection issues have been resolved. > > That said, you should also take on the task of stress testing the latest > version against your department's workflows and datasets. Unreported issues > are usually not addressed ;) > > +1 > It's especially crucial to do this now as we're 4 weeks away from seeing > 3.4 being retired in favor of 3.10. > > Btw, maybe did I miss it but was there a call for testing, in the "News" panel? Gretings, Harrissou Cheers > > On Fri, Jan 24, 2020, 22:42 C Hamilton <[email protected]> wrote: > >> Has 3.10.2-2 been verified to have solved the projection issues. I have >> been holding off introducing it to our departments until it was fixed. I >> will also wait for several weeks as well to make sure there isn't some >> other serious issue. >> >> Thanks, >> >> Calvin >> _______________________________________________ >> 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-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-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
