Re: LilyPond 2.20 release process

On Sat, 31 Dec 2016 at 18:52 Trevor Daniels wrote: > > Phil Holmes wrote Saturday, December 31, 2016 11:03 AM > > > >I think there are a few bugs that need attention prior to stable release. > > https://sourceforge.net/p/testlilyissues/issues/4975/ is one I'm aware > of, >

Re: LilyPond 2.20 release process

Phil Holmes wrote Saturday, December 31, 2016 11:03 AM >I think there are a few bugs that need attention prior to stable release. > https://sourceforge.net/p/testlilyissues/issues/4975/ is one I'm aware of, > and there are a number of ones marked as critical. There are four bugs marked as

OLL features (was: LilyPond 2.20 release process)

Hi all, Am 31.12.2016 um 10:31 schrieb David Kastrup: > I would urge the openlilylib > crew to assess their current work and see whether they consider any > parts suitably stable and robust and useful to include in the next > release. I see three items in openLilyLib that I would like to discuss

Re: LilyPond 2.20 release process

"Phil Holmes" writes: > I think there are a few bugs that need attention prior to stable > release. https://sourceforge.net/p/testlilyissues/issues/4975/ is one > I'm aware of, and there are a number of ones marked as critical. Sounds like something that might be addressed

Re: LilyPond 2.20 release process

;d...@gnu.org> To: <lilypond-devel@gnu.org> Sent: Saturday, December 31, 2016 9:31 AM Subject: LilyPond 2.20 release process In order to properly wrap up my maintainership of LilyPond, I would like to make sure that LilyPond 2.20 is released in an orderly manner. Work that does not appear to

LilyPond 2.20 release process

In order to properly wrap up my maintainership of LilyPond, I would like to make sure that LilyPond 2.20 is released in an orderly manner. Work that does not appear to make sense to include in 2.20.1: a) Guile 2.0 support in release-quality manner and enabled by default. However, in order to