Re: 2.12 uploaded

[Reinhold Kainhofer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Mittwoch, 24. Dezember 2008 03:27:33 schrieb Han-Wen Nienhuys:
> I have just cut a 2.12.0 release, uploaded it to lilypond.org, and
> switched over the redirects to v2.12.

Great to hear!
Did you build it with gub? I'm asking, because my gub builds failed (for 
example in input/regression/musicxml/ trying to build the .zip file of the 
.xml files... the makefile rule to create that .zip file breaks for 
builddir!=srcdir)

> I leave it to anyone interested to pose as the official representative
> of the lilypond community and post a release announcement.

Don't we have some drafts of such an announcement available (Graham? Till?)


What about bug fixes that went in after 2.12 was branched? Shouldn't most of 
them be cherry-picked into 2.12? (For example, the convert-ly rule for :bigger 
or the GCC 4 compile fix)

For such a big release it would have been nice to have a fixed date beforehand 
so that one can make sure that everything that is supposed to be in there is 
really in. For example, I have two local patches, which I think should go in 
2.12.

As things are currently in LilyPond, I don't think that the term "stable 
version" makes much sense. All our releases seem to me like snapshots of the 
current development version at some random times, while bugfixes and all the 
polishing go only into the development version.

I would have preferred an internal announcement a week ago or so, that 2.12 
will be branched on this or that day and that everyone should make sure that 
what he thinks should be in 2.12 is committed by then.

Cheers,
Reinhold
- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, address@hidden, http://reinhold.kainhofer.com/
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
 * http://www.fam.tuwien.ac.at/, DVR: 0005886
 * LilyPond, Music typesetting, http://www.lilypond.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFJUjuiTqjEwhXvPN0RAoL8AJwKkAfYIEokg8mQcBkvr9Uu8CALfACbB2f7
/Udw5D7C6fK7IgqxoGh3uZA=
=BSEY
-----END PGP SIGNATURE-----