On Mon, Aug 17, 2009 at 07:58:32PM -0300, Han-Wen Nienhuys wrote:
> On Mon, Aug 17, 2009 at 7:58 PM, Han-Wen Nienhuys wrote:
>
> >> Yes. All it takes is bookmarking the site, checking it whenever
> >> there's a release, and reporting any broken examples. However,
> >> nobody is willing to commit
On 2009-08-18, Reinhold Kainhofer wrote:
> Am Montag, 17. August 2009 23:49:28 schrieb Trevor Daniels:
> > Graham Percival wrote Monday, August 17, 2009 10:35 PM
> > > On Mon, Aug 17, 2009 at 05:17:08PM +0200, Reinhold Kainhofer
> > > wrote:
> > >> The 2.13.3 results are at:
> > >>
> > >> http://li
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Montag, 17. August 2009 23:49:28 schrieb Trevor Daniels:
> Graham Percival wrote Monday, August 17, 2009 10:35 PM
> > On Mon, Aug 17, 2009 at 05:17:08PM +0200, Reinhold Kainhofer
> > wrote:
> >> The 2.13.3 results are at:
> >>
> >> http://lilypond.o
On Mon, Aug 17, 2009 at 7:58 PM, Han-Wen Nienhuys wrote:
>> Yes. All it takes is bookmarking the site, checking it whenever
>> there's a release, and reporting any broken examples. However,
>> nobody is willing to commit to do this. 15 minutes whenever
>> there's a release, which happens at mos
On Mon, Aug 17, 2009 at 6:35 PM, Graham
Percival wrote:
>> Graham was referring to the fact that nobody seem to bother about looking at
>> those automatically-created regression results before or after a release.
>
> Yes. All it takes is bookmarking the site, checking it whenever
> there's a rele
2009/8/17 Graham Percival :
> I think that's normal for a .0 release.
I assumed the same, but 2.12.0 has results against 2.11.66 (OK, that
didn't officially exist since I made a mistake doing a version bump
before 2.12) and 2.11.65.
> Oh, yet another problem with the lack of release steps. It'l
On Mon, Aug 17, 2009 at 10:55:37PM +0100, Neil Puttock wrote:
> 2009/8/17 Graham Percival :
>
> > Yes. All it takes is bookmarking the site, checking it whenever
> > there's a release, and reporting any broken examples. However,
> > nobody is willing to commit to do this. 15 minutes whenever
>
2009/8/17 Graham Percival :
> Yes. All it takes is bookmarking the site, checking it whenever
> there's a release, and reporting any broken examples. However,
> nobody is willing to commit to do this. 15 minutes whenever
> there's a release, which happens at most once every two weeks.
It proba
Graham Percival wrote Monday, August 17, 2009 10:35 PM
On Mon, Aug 17, 2009 at 05:17:08PM +0200, Reinhold Kainhofer
wrote:
Am Montag, 17. August 2009 16:08:36 schrieb Michael Käppler:
>
> > (nobody checks the regression tests for each release, for
> > example
> > -- and that's trivially don
On Mon, Aug 17, 2009 at 05:17:08PM +0200, Reinhold Kainhofer wrote:
> Am Montag, 17. August 2009 16:08:36 schrieb Michael Käppler:
> >
> > > (nobody checks the regression tests for each release, for example
> > > -- and that's trivially done with a web browser!)
> >
> > That reminds me of an idea I
Reinhold Kainhofer wrote:
Isn't this exactly what we already have (make test-baseline to create the
Argh, how embarrassing! Sorry for the noise.
Regards,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/li
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Montag, 17. August 2009 16:08:36 schrieb Michael Käppler:
> [CC to -devel]
>
> > (nobody checks the regression tests for each release, for example
> > -- and that's trivially done with a web browser!)
>
> That reminds me of an idea I recently had: W
[CC to -devel]
(nobody checks the regression tests for each release, for example
-- and that's trivially done with a web browser!)
That reminds me of an idea I recently had: Wouldn't it be possible to
automatically generate a sort of "checksum" for each regression-test
output-file and compar
13 matches
Mail list logo
