On Sat, Feb 10, 2018 at 09:24:52PM +, Jean-Marc Lasgouttes wrote:
> Le 10/02/2018 à 19:51, Scott Kostyshak a écrit :
> > One pending issue is that we appear to have broken the pixmap cache
> > (compared to 2.2.3). We are considering not fixing it and instead
> > ignoring the preference since we
On Sat, Feb 10, 2018 at 09:17:04PM +, Jean-Marc Lasgouttes wrote:
> However warnings could go to standard error,
I did not check, but in a quick look we write errors with logger.error()
and I assume that goes to standard error.
> and this could be made
> available somehow.
What do you mean?
Le 10/02/2018 à 19:51, Scott Kostyshak a écrit :
One pending issue is that we appear to have broken the pixmap cache
(compared to 2.2.3). We are considering not fixing it and instead
ignoring the preference since we have no reason to believe that the
preference is useful anymore. This late in the
Le 10/02/2018 à 19:44, Scott Kostyshak a écrit :
I'm wondering if it would be useful to add an option to configure.py
that would turn warnings into errors; and additionally whether it would
make sense to turn this option on by default when using
--enable-build-type=pre (autotools) and -DLYX_RELEA
On Sat, Feb 10, 2018 at 07:28:01PM +, Joel Kulesza wrote:
> On Sat, Feb 10, 2018 at 11:51 AM, Scott Kostyshak wrote:
>
> > One pending issue is that we appear to have broken the pixmap cache
> > (compared to 2.2.3). We are considering not fixing it and instead
> > ignoring the preference sinc
On Sat, Feb 10, 2018 at 11:51 AM, Scott Kostyshak wrote:
> One pending issue is that we appear to have broken the pixmap cache
> (compared to 2.2.3). We are considering not fixing it and instead
> ignoring the preference since we have no reason to believe that the
> preference is useful anymore.
Am Samstag, den 10.02.2018, 13:51 -0500 schrieb Scott Kostyshak:
> Am I missing any other potential blocker?
I'm not aware of any.
> What is your feeling on how stable our 2.3.x branch currently is?
I think it is stable enough to be released. I use it for daily work for
quite some time now, and
Dear all,
rc2 has been out for a week and a half. We have discovered and fixed a
couple of important bugs that were discovered by our testers. For
example, we had a Python issue in configure (fixed at 42718b1d) and text
could not be entered in the advanced find pane (fixed at 14e0a270). In
additio
On Thu, Feb 01, 2018 at 07:09:47PM +, Scott Kostyshak wrote:
> Thanks to Jean-Pierre's hawk eyes, we found a potential issue in
> configure.py [1]. I did not see this because I don't manually check the
> configure log (although this would be a good thing to do from time to
> time).
>
> I'm won
