Lilypond release
I've been in the habit of trying to make a release every 2 weeks, normally on a Sunday. This morning I've been out breaking a world record (https://twitter.com/search?q=%23flutteroffairies&src=hash) and I'm also going to check the problem of my build machine crashing on orchestra.ly. So I'll almost certainly make the release tomorrow, not today. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
LilyPond release
We were due a release today, but what with Carol services (two today) and other stuff I had to do, it slipped my mind. I'll plan to do one early in the coming week. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Lilypond release
"Phil Holmes" writes: > I've been in the habit of trying to make a release every 2 weeks, > normally on a Sunday. This morning I've been out breaking a world > record (https://twitter.com/search?q=%23flutteroffairies&src=hash) and > I'm also going to check the problem of my build machine crashing on > orchestra.ly. So I'll almost certainly make the release tomorrow, not > today. Given the current state of repo and bugs being worked on, it might make even more sense to just shift this to next weekend altogether. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Lilypond release
- Original Message - From: "David Kastrup" To: Sent: Sunday, June 23, 2013 2:54 PM Subject: Re: Lilypond release "Phil Holmes" writes: I've been in the habit of trying to make a release every 2 weeks, normally on a Sunday. This morning I've been out breaking a world record (https://twitter.com/search?q=%23flutteroffairies&src=hash) and I'm also going to check the problem of my build machine crashing on orchestra.ly. So I'll almost certainly make the release tomorrow, not today. Given the current state of repo and bugs being worked on, it might make even more sense to just shift this to next weekend altogether. -- David Kastrup Yeah - suits me. Given we have a couple of tricky bugs that seem to cause builds to fail, I'm a bit loathe to stoke GUB up. Next weekend it is. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Fwd: next lilypond release
Any estimates? Original-Nachricht Betreff:next lilypond release Datum: Wed, 26 Nov 2014 14:45:50 +0800 Von:Jan Hakenberg An: u...@openlilylib.org Hi Urs I have been using Lilypond since Dec 2013. https://www.youtube.com/watch?v=YSPPoTvAFbQ I noticed that no minor release has been issued for a long time. If possible, can you let me know if or when an update is coming next? thank you very much! many greetings, Jan ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fwd: next lilypond release
On 26/11/14 07:02, Urs Liska wrote: Any estimates? Original-Nachricht Betreff: next lilypond release Datum: Wed, 26 Nov 2014 14:45:50 +0800 Von: Jan Hakenberg An: u...@openlilylib.org Hi Urs I have been using Lilypond since Dec 2013. https://www.youtube.com/watch?v=YSPPoTvAFbQ I noticed that no minor release has been issued for a long time. If possible, can you let me know if or when an update is coming next? thank you very much! many greetings, Jan ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel Nothing until Phil is back from his holidays which should be any day now. As to minor release for 2.18, I don't think we are going to do any... The next step is 2.20 I guess. But DK will be best placed to advise on that I think. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fwd: next lilypond release
James writes: > Nothing until Phil is back from his holidays which should be any day now. > > As to minor release for 2.18, I don't think we are going to do any... > > The next step is 2.20 I guess. > > But DK will be best placed to advise on that I think. As long as we don't have 2.20, minor releases for 2.18 might happen for "stops compiling with current toolchains": we want to have at least one stable version of LilyPond that can compile on current systems (apart from GUILEĀ 2.0 as to yet). -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LilyPond Release Candidate for version 2.8
On Friday 17 February 2006 19.24, Han-Wen Nienhuys wrote: > Hi y'all, > > I've just uploaded LilyPond 2.7.35, which squashes a truckload of bugs. > The plan is to release 2.8 at the end of this month, so please give it a > whirl to see if it has any showstoppers. Hi, This is cool. I just went through the bug repository, and the number of known bugs has decreased from 95 to 70. Well done, Han-Wen!! My list of objections to releasing 2.8 is currently rather short: - volta-bracket-break in bug cvs - Bar numbers are right-aligned to the left of barlines, as can be seen in bar-number-breathe.ly - MIDI corrupts memory (see recent mail) -- Erik ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel