We also have this blocker issue in 2.2.0 because it wasn't completely fixed after all: http://hub.qgis.org/issues/9396
Best wishes, Anita On Tue, Feb 25, 2014 at 1:44 PM, Etienne Tourigny <etourigny....@gmail.com> wrote: > There are going to be a few other bugs, hopefully fixed in 2.2, so > eventually a point release will be worthwhile. With (semi-)automated builds > it's not *that* much trouble I think. > > > On Tue, Feb 25, 2014 at 9:40 AM, Sandro Santilli <s...@keybit.net> wrote: >> >> On Tue, Feb 25, 2014 at 12:09:30PM +1000, Nathan Woodrow wrote: >> > hmmm that is a real bugger. Yeah I think kind of thing warrants a bug >> > fix >> > release. This will kill QGIS for most users who do data entry, which is >> > most of the people I know. >> >> +1 >> >> A 2.2.1 could come out after 1 week of no activity in the stable branch >> after >> any activity. >> >> If it takes 4 months to get to that state (ie: nobody pushes a fix for >> that >> or more than one fix a week gets committed weekly) then no 2.2.1 would >> ever >> come out. >> >> --strk; >> _______________________________________________ >> Qgis-developer mailing list >> Qgis-developer@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/qgis-developer > > > > _______________________________________________ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer _______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer