While helping troubleshoot the bug before the release, I got the impression that Text handling was always a second-class feature of inkscape - it's never had the attention it needed to be considered a reliable professional tool. Advice for clunky workarounds has become how it works (jiggle it with the arrow keys so it saves properly, for example).

There was some attention paid to fixing the tool, just not enough paid to making sure old template files still work, and fixed automatically upon the next save.

All this is much easier said than done. I guess I just accepted that old templates were not going to show properly for this release, because I really appreciate the progress that has been made to making the tool more usable.

And that's what I hear from people who use inkscape for templates in the GNOME project- They are simultaneously upset that the old templates don't show correctly, but "at least the text tool is more usable now"

So I guess going forward it makes sense to assign a higher priority to the text features of inkscape as well as a backward compatibility for previous templates, to bring them up to speed with the necessary changes to the text tool, without the need for dialogs.

My 2p
-C





On 21 Jan 2017 4:57 a.m., "Martin Owens" <doctormo@...400...> wrote:
Developers,

As someone how changed the line-height code prior to release, I feel
somewhat responsible for the issue in 0.92. I really didn't have enough
time to focus on bugs before the release, but should have spent more
time on things I'd changed. I'm really sorry Inkscape.

This thread isn't for figuring out how we're going to solve the issue
though. I'll let the 0.91.1 discussion cover that.

What I'd like to pick apart is our bug management and how a release
blocker like this line-height issue didn't put an all stop on our
release schedule while we figured it out.

There's a couple of possibilities:

 1. The bug wasn't discovered in time
 2. The bug wasn't reported in time
 3. The reported bug wasn't triaged in time
 4. The bug wasn't prioritised as important
 5. There wasn't a way to communicate a major issue to the release
manager.
 6. We just didn't have the resources to do the release properly and
let things slide.

What information can Mc and su_v add about the issue? What can we fix
to make the process better?

I feel bad asking for your help to really figure this out, but I think
this might help us as a project overall if we know what happened and
how to defend against it.

Thanks everyone.

Best Regards, Martin Owens
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...1656...784...sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel