Pre-release issue and push notes
[email protected] Sat, 26 Jan 2019 03:37:34 -0800
| Newsgroups | gmane.comp.fonts.fontforge.devel |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============3435124268373199914==
Content-Type: multipart/alternative;
boundary="------------7F55CA2CA05FAFBA7FB18F60"
Content-Language: en-US
This is a multi-part message in MIME format.
--------------7F55CA2CA05FAFBA7FB18F60
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
I've suggested a number of fixes for existing issues, some of which have
been merged, and also been through the list of recent issues a few
times. Since a release seems imminent I'm writing with some notes on
remaining issues and pull requests. None of this is meant to be
comprehensive -- issues I say nothing about may still be important.
Blockers
I recommend against releasing without merging #3398 or some equivalent.
Given that WOFF2 support is relatively new I suspect issue #3422 may be
quite serious as well, and should either be fixed or (optional) support
of WOFF2 postponed. Given that that issue has no current pull request
it would benefit from some attention now. (User @Yay295 has done some
testing with pre-release code and filed this issue.)
Other
I would not recommend holding the release for any other issue or
unmerged push request that I've filed or recently commented on.
Obviously the more fixes the better.
Given that the shift away from Python 2 is that much further along some
serious thought should be put into #3409. Along those lines it would be
helpful if someone with Mac OS X access could identify the details of
the failure of #3410, which is a test of #3409.
#3395 would be a shame to loose but is close enough to merging that
there shouldn't be a problem.
Issue #3420 is a potential docs fix and I would appreciate if someone
could comment on it. Some behaviors attached to the Meta key are
super-useful but don't work as described, at least on my machine. The
question is whether to change the code or the docs.
Most of #3399 can be ignored but it would be nice to avoid the
graphicore warning message. (Basically it looks sloppy to have a warning
dialog pop up every time you start a program after a normal build and
install.)
My other push requests #3133, #3425 and #3347 are for specific and
(likely) rare problems.
That's it!
Skef
--------------7F55CA2CA05FAFBA7FB18F60
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>I've suggested a number of fixes for existing issues, some of
which have been merged, and also been through the list of recent
issues a few times. Since a release seems imminent I'm writing
with some notes on remaining issues and pull requests. None of
this is meant to be comprehensive -- issues I say nothing about
may still be important.</p>
<h3>Blockers</h3>
<p>I recommend against releasing without merging #3398 or some
equivalent. Given that WOFF2 support is relatively new I suspect
issue #3422 may be quite serious as well, and should either be
fixed or (optional) support of WOFF2 postponed. Given that that
issue has no current pull request it would benefit from some
attention now. (User @Yay295 has done some testing with
pre-release code and filed this issue.) <br>
</p>
<h3>Other</h3>
<p>I would not recommend holding the release for any other issue or
unmerged push request that I've filed or recently commented on.
Obviously the more fixes the better.</p>
<p>Given that the shift away from Python 2 is that much further
along some serious thought should be put into #3409. Along those
lines it would be helpful if someone with Mac OS X access could
identify the details of the failure of #3410, which is a test of
#3409. </p>
<p>#3395 would be a shame to loose but is close enough to merging
that there shouldn't be a problem. <br>
</p>
<p>Issue #3420 is a potential docs fix and I would appreciate if
someone could comment on it. Some behaviors attached to the Meta
key are super-useful but don't work as described, at least on my
machine. The question is whether to change the code or the docs. <br>
</p>
<p>Most of #3399 can be ignored but it would be nice to avoid the
graphicore warning message. (Basically it looks sloppy to have a
warning dialog pop up every time you start a program after a
normal build and install.) </p>
<p>My other push requests #3133, #3425 and #3347 are for specific
and (likely) rare problems. <br>
</p>
<p>That's it!</p>
<p>Skef<br>
</p>
</body>
</html>
--------------7F55CA2CA05FAFBA7FB18F60--
--===============3435124268373199914==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
--===============3435124268373199914==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
fontforge-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html
--===============3435124268373199914==--