Re: improving our workflow with better tools - let's test things.

[James]

On 23/10/13 05:48, Keith OHara wrote:
> Janek Warchoł <janek.lilypond <at> gmail.com> writes:
>
> > I'm back... better late than never.
> >
> > Let's try out some code-development platforms and see if using them
> > would make developing LilyPond easier.  GitHub.com is out of question,
> > so we have to check gitlab.com and gitorious.org.
> I tried putting a patch on github.com but got no review
>   http://code.google.com/p/lilypond/issues/detail?id=3606
>
> Another good test case is
>   http://code.google.com/p/lilypond/issues/detail?id=3630
>
> This looks like an adjustment of padding in response to the skyline patch,
> which maybe could be applied and tested without re-compiling LilyPond,
> and where the questions are "which items need this padding?", and "are
> there any bad surprises in the regression tests?".
The tracker is not set to Patch-new, so I won't test it (and I the test 
scripts won't be able to get the patches from here yet anyway) and 
therefore people generally won't 'review' it unless the tracker is set 
to review.

Perhaps I am confused?

James