Hi all,
From my perspective (mainly bug reports and IRC support, but also a
lengthy irc discussion with deevad [from
http://www.peppercarrot.com/en/article396/new-inkscape-0-92-breaks-your-prev...
]), the main noticeable thing about .92 was the line height breakage
problem. I really think that it would be a good thing to include su_v's
extension (or port it to a cpp internal function) and automatically
apply it when opening files made with previous versions, and release the
.91.1RC just after that (as soon as possible, even possibly before your
proposed timing).
Ideally, we could also change the file import dialog to include
instructions so that user would know what they should choose. Something
along the lines of "If your file dimensions are based on pixels (you're
not planning to use a cnc or print directly from inkscape), choose
"ignore"; else choose "set viewBox", except if you know what you're
doing." [might not be compatible with the "RC asap" because of the
strings to translate]
In the terms of the pre-0.92 to 0.92 file update, we identified with
su_v, by decreasing importance, the following items:
(*1*) we need to apply, by default, the legacytext-fix (
https://gitlab.com/su-v/inx-legacytext/ ) to all pre-.92 files on open,
or an equivalent (internal) solution;
(*2*) The import dialog is very unclear on what users should do, might
not cover all cases (I tried to draft a diagram of possible cases and
ended up with the nightmarish http://imgur.com/h6uEOHm but I'd like
Tav's input on when to do what, and what to advise people doing by
default), and does not gives hints on what to choose;
(*3*) we need to bump the export-xdpi prefs setting and others (once
only[which means add a versionning mechanism into the prefs: "if prefs
are older than inkscape, do it"], if possible (others : bitmap copy
resolution,bitmap import resolution));
(*4*) we need a commandline way to bump files from .91 to .92;
(*5*) Add prefs for (2), similar to the embed/link choices, so that
users don't have to specify several times when working with sets of
similar files
(*6*) port all that to trunk and clean involved code (for instance, move
all that updating code to a separate file-update.cpp instead of file.cpp )
--
Marc
On 01/06/2017 03:44 AM, Bryce Harrington wrote:
> The 0.92.x stable branch is reopened for changes. Consider it as under
> feature freeze but not string freeze.
>
> Bugfixes are welcome to be added. Please continue to check with me
> before landing things, but for the next few weeks I expect to be in
> rubber stamp mode and approve most anything that looks sensible. We do
> need to be cautious about not introducing regressions at this point.
> Write good changelog messages explaining the fixes in good detail
> please.
>
> Translation updates (and entirely new translations) are fine to land
> directly, no need to check with me. There are already a handful on the
> branch already that unfortunately came in just after I had cut the
> tarball.
>
> Extension updates and new extensions are probably low enough regression
> risk that I'll try to be liberal in approving them. The ones we have to
> be cautious about are the highly used extensions, since we risk breaking
> people's workflow.
>
> A few specifics I'm aware of, that sound worth including:
>
> + Tutorials and other .svg files we ship have the dpi scaling issue,
> and need updated for 0.92.1
> + suv mentioned an extension to provide users a workaround to some
> line spacing issues, iirc.
> + A mechanism to backup / reset prefs settings
> + Fixes to some strings that were found post-string freeze
> + A gpl3 widget needs removed (or relicensed)
>
> I'd like to avoid maintaining a bugs-needing-fixed list, but rather
> focus time more on patch review and testing. I figure the important
> thing is to get 0.92.1 out in a timely manner, and if there's still bugs
> needing attention we can always do a 0.92.2 some time later on.
>
> Proposed Timing:
>
> Mon Jan 2 Feature Freeze
> 0.92.1pre0 Mon Jan 23 Hard Freeze
> 0.92.1pre1 Mon Jan 30 String Freeze
> 0.92.1pre2 Mon Feb 6 Release Candidate
> 0.92.1 Fri Feb 10 Cut Release
> Mon Feb 13 Announcement
>
> I know we've not got a strong history of staying to schedule, but I'm
> going to try hard to hit these dates at least within a day or so. That
> means we'll have to be strict about string changes after String Freeze,
> and strict about any changes after the Release Candidate. This schedule
> allows the weekend of Feb 11-12 for prepping website changes, finalizing
> packages, and so on.
>
> Anything you can think of missing from this plan?
>
> Bryce
>
> ------------------------------------------------------------------------------
> 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@lists.sourceforge.net
>
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>