On Mon, Feb 8, 2010 at 9:29 AM, David Kastrup <d...@gnu.org> wrote:
> +Even if you are not familiar with git or are not able to compile
> +LilyPond you can still help to narrow down the cause of a regression
> +simply by downloading the binaries of different LilyPond versions
> +and testing them for the regression. Knowing which version of
> +LilyPond first exhibited the regression is helpful to a developer
> +as it shortens the @code{git bisect} procedure described above.
>
> I don't think that this is useful advice since binaries often are
> incompatible with Scheme/Lilypond trees of other versions, and since
> many regressions are not introduced in the binaries.
I think 'binary' here is asumed to mean the precompiled one, which
comes with the matching data files.
I am not sure if I agree with the comment, but for a different reason.
The release rate of the LilyPond has gone down from once per week to
once per month (at most). With that few releases, the release number
that introduced a bug is not that useful a data point.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
