Guenter Milde wrote:
> What is the policy regarding change-tracking for Development.lyx?
Not needed: It is not translated. If we want to know latzer who edited a
certain part then we can use git.
Georg
On 2015-11-11, Scott Kostyshak wrote:
> On Tue, Nov 10, 2015 at 03:30:24PM +, Guenter Milde wrote:
>> On 2015-11-10, Scott Kostyshak wrote:
>> > On Mon, Nov 09, 2015 at 11:19:16AM +0100, Vincent van Ravesteijn wrote:
>> >> And yes of course there is an implicit rule that when your commit breaks
On Tue, Nov 10, 2015 at 03:30:24PM +, Guenter Milde wrote:
> On 2015-11-10, Scott Kostyshak wrote:
> > On Mon, Nov 09, 2015 at 11:19:16AM +0100, Vincent van Ravesteijn wrote:
> >> And yes of course there is an implicit rule that when your commit breaks
> >> something or has problems whatsoever
On 2015-11-10, Scott Kostyshak wrote:
> On Mon, Nov 09, 2015 at 11:19:16AM +0100, Vincent van Ravesteijn wrote:
>> >> So my preferred policy would be:
>> if a
>> >> commit is found to have broken a test, either the situation is resolved
>> within
>> >> a day (i.e. the bug is fixed or the test is f
Note: quoting is not correct (probably because of replying on phone).
On Mon, Nov 09, 2015 at 11:19:16AM +0100, Vincent van Ravesteijn wrote:
> >> Ideally, I would like for commits that break tests to be on a separate
> git
> >> branch. Once the bugs exposed by a commit are fixed or the tests are
On Mon, Nov 09, 2015 at 09:13:37AM +, Guillaume Munch wrote:
> Le 02/11/2015 03:41, Scott Kostyshak a écrit :
> >Thanks to all of those participating in the discussions about tests. I have
> >learned a lot the last couple of weeks. Thank you also to those who have
> >tried
> >to run the tests.
>> Ideally, I would like for commits that break tests to be on a separate
git
>> branch. Once the bugs exposed by a commit are fixed or the tests are
fixed, or
>> the .lyx files are fixed, then the branch could be merged to master. This
>> allows us to presere a "0 failing tests" situation on the m
Le 02/11/2015 03:41, Scott Kostyshak a écrit :
Thanks to all of those participating in the discussions about tests. I have
learned a lot the last couple of weeks. Thank you also to those who have tried
to run the tests. This to me is a great step forward. I know that the export
tests are sloppy c
Guenter Milde wrote:
> On 2015-11-02, Georg Baum wrote:
>
>> 1) Fix the first half of bug #9744. This is an easy and safe change
>
> Actually, "allowing parallel configuration of TeX and non-TeX fonts" is a
> precondition for the proposed config value "automatic" for "use non-TeX
> fonts":
>
>
On 2015-11-02, Georg Baum wrote:
> Scott Kostyshak wrote:
>> So in summary, regarding the XeTeX + TeX fonts, I propose the above policy
>> to start with; and if we find that there really is such a low signal to
>> noise ratio then we can change our minds and ignore them. But we will
>> never know
On Mon, Nov 02, 2015 at 09:26:07PM +0100, Kornel Benko wrote:
> > It seems to me that the underlying causes of the XeTeX + TeX fonts tests
> > will
> > not be fixed anytime soon (and that this is OK) so we have two options if we
> > want to clean up the test output. We can either invert the curren
On Mon, Nov 02, 2015 at 09:21:23PM +0100, Georg Baum wrote:
> Scott Kostyshak wrote:
>
> > So in summary, regarding the XeTeX + TeX fonts, I propose the above policy
> > to start with; and if we find that there really is such a low signal to
> > noise ratio then we can change our minds and ignore
Am Sonntag, 1. November 2015 um 22:41:39, schrieb Scott Kostyshak
> Thanks to all of those participating in the discussions about tests. I have
> learned a lot the last couple of weeks. Thank you also to those who have tried
> to run the tests. This to me is a great step forward. I know that the
Scott Kostyshak wrote:
> So in summary, regarding the XeTeX + TeX fonts, I propose the above policy
> to start with; and if we find that there really is such a low signal to
> noise ratio then we can change our minds and ignore them. But we will
> never know what the signal to noise ratio is if we
Thanks to all of those participating in the discussions about tests. I have
learned a lot the last couple of weeks. Thank you also to those who have tried
to run the tests. This to me is a great step forward. I know that the export
tests are sloppy cheap tests, but I appreciate that some of you agr
15 matches
Mail list logo
