Am Samstag, den 31.10.2020, 13:23 +0000 schrieb Phil Holmes: > Looking at this now. I see that in the 2.22 branch VERSION numbers are > stable 2.22.0 and devel will be 2.21.80. I've never really worked out how > GUB decides to create a new stable version or a development version, but it's > conceivable that it creates the highest numerical version. I'm wondering > whether it would be good to have the stable version number fixed at 2.20.0 > until we're ready to release 2.22.0?
Not sure I can follow here, the current VERSION content is: MAJOR_VERSION=2 MINOR_VERSION=21 PATCH_LEVEL=80 MY_PATCH_LEVEL= VERSION_STABLE=2.20.0 VERSION_DEVEL=2.21.7 I think the normal release procedure should do here, ie bump VERSION_DEVEL to 2.21.80. After the release, PATCH_LEVEL in stable/2.22 should be 81 and the bump of VERSION_DEVEL needs to be applied to master. I agree that the stable version number should remain at 2.20.0 for the time being, in both stable/2.22 and master. > > On 29/10/2020 15:52, Jonas Hahnfeld wrote: > > Am Sonntag, den 25.10.2020, 14:42 +0100 schrieb Jonas Hahnfeld: > > > As the title says. We still need to merge the PO translations (see > > > https://gitlab.com/lilypond/lilypond/-/merge_requests/476 ) and pick > > > them to stable/2.22. If you speak one of the concerned languages that > > > I've been hijacking the translation for (ca, eo, es, it, nl, sv), > > > please consider giving it a short look. I'll also merge the translation > > > branch to stable/2.22 before asking Phil for a release. > > All items from my list are done (above + fixing the translated snippets > > when building in-tree) and stable/2.22 looks good from what I can tell. > > So, I think we're ready for a first release candidate. > > Phil, if you have time, could you run a build on stable/2.22? I will > > stop picking fixes into the branch to avoid any interference (commits > > to translation can of course continue). > > > > Regards > > Jonas >
signature.asc
Description: This is a digitally signed message part
