lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Regtests


From: Phil Holmes
Subject: Re: Regtests
Date: Wed, 29 Aug 2012 15:09:04 +0100

----- Original Message ----- From: "Janek Warchoł" <address@hidden>
To: "Graham Percival" <address@hidden>
Cc: "Phil Holmes" <address@hidden>; "Devel" <address@hidden>
Sent: Wednesday, August 29, 2012 2:52 PM
Subject: Re: Regtests


On Wed, Aug 29, 2012 at 2:15 PM, Graham Percival
<address@hidden> wrote:
On Wed, Aug 29, 2012 at 01:09:20PM +0100, Phil Holmes wrote:
2.17.1.  The official regtest comparison is against 2.15.38, because
of the vagaries of my initial GUB build.

ouch, but not critical in this case.  Mike's monster patch changes
pretty much everything, so a regtest comparison isn't useful.
I mean, it's big enough that it would be more effective to reset
the web regtest checker and recruit a new wave of users to
evaluate them.
[...]
Given Mike's monster, I doubt that the pixel comparator will be
useful for 2.17.1.

i know that i'm late - forgot about it, sorry :( - but nevertheless it
may still be possible:
what about having a separate release containing only Mike's patch?
Since 2.17.1 isn't released yet (at least officially), maybe we could
do sth like this:
- branch 6f4893fa86378aa4a637eedbde5efc4680efa5bf (last commit before
skylines) as release/2.17.1, release it
- then release 28f3294954eff1f263d3b2e3de1c520f4d2fbdfc (skylines) as 2.17.2
- continue as usual
?
It would be handy for regtest comparisons and other things like that.

Janek


2.17.1 is 90-odd % released - if my DSL uplink was faster it would be visible on the server now.

--
Phil Holmes



reply via email to

[Prev in Thread] Current Thread [Next in Thread]