Re: Testing needed for 2.13.15

[James Lowe]

Hello,

Sorry, I have gone back through this thread and I have misunderstood 
what was required. I *didn't* run the cmd line

lilypond [file1] [file2] [file3]

I simply ran multiple instances of compiling using lilypad (cmd-r). 
That's what a Mac user does :)

In fact cli doesn't work for me on Mac OS - in a terminal I just get the 
switch list displayed for lilypond when I run ANY command in Terminal, 
but I also got this in 2.12.x too. No errors.

But that said, this is just because I never bother with the CLI.

So sorry about that.

However I will try this for Windows and go back and revisit Mac OS when 
I am back home this weekend, unless someone else beats me to it.

James



James Lowe wrote:
> Patrick,
>
> For Mac OS X 10.5 everything I did for 2.13.14 came out the same as 
> 2.13.15.
>
> I'll try to do the same files for Win7 today.
>
> James
>
> Patrick McCarty wrote:
> > On Thu, Mar 4, 2010 at 4:07 PM, James Lowe <address@hidden> 
> > wrote:
> > > Happy to test OS X 10.5.8 and Windows 7.
> > >
> > > However I'd need to know what to test (i.e. to see it broken first to 
> > > know what I am looking for).
> >
> > I think my original message was too verbose to really make any sense
> > of.  Sorry about that.
> >
> > This is all you have to do:
> >
> > 1) With 2.13.14, compile a series of files with:
> >
> >   lilypond file1.ly file2.ly ...
> >
> > 2) Move the output files (file1.pdf, file2.pdf, etc.) to a different 
> > location.
> >
> > 3) With 2.13.15, compile the same set of files with the same command.
> >
> > 4) Verify that the 2.13.15 output is rendered the identically to the
> > 2.13.14 output.  We want to make sure there are no regressions.
> >
> > Thanks,
> > Patrick
>
>
> _______________________________________________
> lilypond-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/lilypond-devel