Thanks Eduard,
Regressions that are critical to the release are noted as blockers. You can help inkscape manage it's bugs overall by making sure key bugs are marked as blocking or critical as needed. I think we should talk more about which bugs should be more important to the next release as we go into freeze.
Our community will always be on the back-foot for regressions because it is open to contributions, only middling at code review and has no (yet) funding for bug fixing. Taken together you can see how we encourage features and discourage bug fixing structurally.
Although we encourage bug fixing socially ;-) so if you've written some code this year, please please fix some bugs for the next release. My own personal plea which will hopefully encourage me to also fix some bugs for the release.
Martin,
On Tue, 2016-05-31 at 20:12 +0200, Eduard Braun wrote:
Hi Nicolas,
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 [1] (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?
I hope I can have a look at some bugs, but I don't have too much time right now... Also German translation needs some more work which is probably as important as fixing bugs now that we're in string freeze...
Best Regards, Eduard
[1] https://bugs.launchpad.net/inkscape/+bug/1571192
Am 30.05.2016 um 16:35 schrieb Nicolas Dufour:
Hi all,
The release process is so fast I just noticed we have already reached string freeze...
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 before releasing.
What about a bug hunt?
Regards,
Nicolas
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;1326 59582;e _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659 582;e _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel