It is indeed a very serious. I know that packaging takes a lot of time and effort, but I wonder if it wouldn't be better to "cancel" 2.8 and jump to 2.8.1. since the bug was already fixed.
This was obviously very unfortunate, but I fear that many people will be extremely annoyed to find this problem in a new release. If 2.8.1 is not feasible right away, I would suggest a big warning about this. Cheers On Sun, Feb 22, 2015 at 9:02 PM, Anita Graser <[email protected]> wrote: > > On Sun, Feb 22, 2015 at 9:17 PM, Pedro Venâncio <[email protected] > > wrote: > >> Filipe, >> >> 2.8 has been realeased already. >> > > I think the release hasn't officially been announced yet though. > > +1 to 2.8.1. But maybe it is better to wait a few more days to see if any >> more serious errors appears, and then release 2.8.1. >> > > On the other hand we know there's a serious issue - so we would at least > have to warn users that this one feature is broken in 2.8.0 ... > > > Best wishes, > Anita > > > > > > > > >> >> >> Best regards, >> Pedro >> >> _______________________________________________ >> Qgis-developer mailing list >> [email protected] >> http://lists.osgeo.org/mailman/listinfo/qgis-developer >> > > > _______________________________________________ > Qgis-developer mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/qgis-developer >
_______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
