On Tue, May 31, 2016 at 08:12:12PM +0200, Eduard Braun wrote:
I totally agree! One of Inkscapes biggest weaknesses are
regressions. While a new release often brings many exciting new
features that people would like to play around with, there are often
severe regressions that not only cancel those achievements but even
leave users with mixed to negative feelings about the new release.
If we could sort out the worst regressions the profit would
therefore be disproportional.
Best example is bug 1571192  (severe performance regression in
GTK2 builds caused by some - in principle very welcome - GTK3 fixes
during the hackfest). I had used trunk builds for my productive work
for quite some time now. Since this regression I stopped using them
and even returned to stable 0.91 builds on some machines. For me a
0.92 release without a fix for that issue would be worthless,
despite the many great features and improvements it would offer.
Therefore also the slightly off-topic question: Are you making any
progress on this issue Krzysztof?
Yes, this is one of the release critical bugs we're already tracking.
This was discussed at the release meeting yesterday. This may have been
due to a Gtk3 fix landed during the hackfest.
I hope I can have a look at some bugs, but I don't have too much
time right now...
Am 30.05.2016 um 16:35 schrieb Nicolas Dufour:
>The release process is so fast I just noticed we have already reached string
>There are 214 reports linked to 0.92 and half of them are regressions.
>I *feel* we should at least try to fix some of the 25 high importance regressions
>What about a bug hunt?
We're skipping doing a bug hunt this time around in order to get the
release out more quickly. It would be great to get more regressions
resolved, but time is a limited commodity, as Eduard points out. We
still have a lot left to do for the release, so there's ample time for
anyone that would like to focus on fixing more bugs before we release.