Am Sonntag, den 01.11.2020, 13:54 +0100 schrieb Jonas Hahnfeld: > Am Sonntag, den 01.11.2020, 12:36 +0000 schrieb Phil Holmes: > > On 01/11/2020 12:30, Jonas Hahnfeld wrote: > > > Am Sonntag, den 01.11.2020, 12:02 +0000 schrieb Phil Holmes: > > > > Thanks. Now uploaded. > > > Thanks to you for staying with us while we resolve such things! > > > > > > > We do need to get the latest/correct VERSION into master, as well as > > > > updating the news details. That should allow the website to be > > > > rebuilt. I'm assuming that the best bet would be to cherry-pick the > > > > news updates from stable/2.22 into release/unstable, and edit and push > > > > VERSION to unstable as well, then create a merge request? > > > Yes, though I'd use a temporary branch because that doesn't have the > > > restriction of release/unstable that cannot be force-pushed. > > No worries. Be good if you could do this. > > Ok, will do.
Now online at lilypond.org; will you announce to lilypond-user to invite wide-spread testing? Jonas > > > > > > Which commits do we need exactly from the release process? > > > > > > 168c4fac7d Release: bump VERSION_DEVEL. > > Think it might be easier just to update VERSION directly, since the current > > patch level is wrong for the updated master. > > Yeah, that could give conflicts. I'll see what git does for me 😄 P.S.: git figured it out by itself 😉
signature.asc
Description: This is a digitally signed message part