On Sat, 2009-12-12 at 07:00 +0000, Graham Percival wrote: > Just so that people know what's planned... > - another beta for 2.12.3 will happen as soon as I can build the tests > and docs. Jan and I will continue to work on this; hopefully it'll be > out in a few days. This will be the last 2.12 release. > > - 2.13.10 will happen fairly soon thereafter; the main goal of this > release will be to test the release plans. > > - the first beta release of 2.14 will happen as soon as either 1) we > have no Regression or High-priority items in the tracker, or 2) all > the issues in the tracker have been re-categorized with the upcoming > new guidelines. > > - after 2.14, we'll begin having much shorter unstable development > phases. I know I said this last year and it didn't happen, so I have > pretty low credibility on this score, but the difference is that *now* > I can build GUB. > > To assist in this, in the near future I'll set up a daily out-of-tree > building system for lilypond (I've done it before for marsyas). If > any build fails, it will send rude messages to lilypond-devel with a > list of the names of everybody who committed things since the last > successful build. :)
Would it be feasible (using git-bisect) to pin down the exact failing commit? _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
