Quack, I think the release team should have been involved much much earlier.
It seems having Lilypond working with recent Guile before the release is not going to happen. Even if it built properly there would maybe have runtime bugs to solve.
If people are willing to maintain Guile 1.8 into stable during another release lifetime, I guess the release team would be ok with it. Maybe it would be possible to provide a backport of Guile 2.x and newer Lilypond later (when it works) and drop Guile 1.8 and current Lilypond from stable in a subsequent point release. This could be announced in the release notes from the start, so no surprise.
Anyway, I'm Cc-ing the release team so they don't discover the problem much later.
\_o< -- Marc Dequènes
