Il 30/01/2018 04:24, Nyall Dawson ha scritto:
> (If anyone has leads on commercial organisations who would possibly be
> interested in sponsoring additional time prior to release - please
> pass them on! Our regression list is still quite lengthy.)
I would like to join the others to congratulate Nyall and all the
other developers that participated in the fixing effort: I know for
sure that beside the paid hours you have worked many others on a
> Our regression list is still quite lengthy
maybe is the right time for little resume.
We have 40 tickets tagged as regression for QGIS3 and 44 for QGIS 2
(almost all confirmed to affect some point release of 2.18). It is
possible/probable that some of the regressions tagged as affecting
2.18 are also confirmed on master.
High priority tickets are 148 (54 master), but only 73 are also tagged
as "Crashes QGIS or corrupts data" which (at least for me) is the
parameter to tag priority as "high".
There are also 77 tickets (32 master) that are awaiting feedback for
more than 15 days, is likely (past experience say so) that several of
them can be closed as invalid.
On 1 February 2018 at 21:01, Giovanni Manghi <[hidden email]> wrote:
> I would like to join the others to congratulate Nyall and all the
> other developers that participated in the fixing effort: I know for
> sure that beside the paid hours you have worked many others on a
> volunteer basis.
Just to add to this - I think it's very important to note that there's
been extended volunteer efforts by other core developers too who
haven't been part of the funded sprints. I'd love to list names, but
am scared I'll miss someone off...
In summary... next time you see a QGIS developer at a hackfest or
conference, make sure you buy them a beer. Or give them a big hug and
reassure them "it's ok... we're back to normal release patterns
again... there's no more major releases for the next 2-4 years...". ;)