Re: Future tag names for releases

[Jonas Hahnfeld]

Am Mittwoch, dem 16.03.2022 um 23:37 +0100 schrieb Han-Wen Nienhuys:
> On Wed, Mar 16, 2022 at 9:57 PM Jonas Hahnfeld via Discussions on
> LilyPond development <lilypond-devel@gnu.org> wrote:
> > while trying to round up the procedure for future releases, I've come
> > across one point that I don't particularly like, and that are the tag
> > names in the git repository. For example, the latest version 2.23.6 is
> > tagged as release/2.23.6-1, which leads to the quite ugly and long link
> > https://gitlab.com/lilypond/lilypond/-/releases/release%252F2.23.6-1
> > because the forward slash needs to be URL-encoded.
> 
> I don't care much, but if we paint the bikeshed, can we prefix the
> version with a non-digit, eg.
> 
>   refs/tags/v2.23.6
> 
> the leading digit always has me do a double take to check it's not a
> number of a hex commit hash.

Yes, we can do that (the Linux kernel and git actually do the same).
I'll keep the 'v' prefix out of the milestones and the packages though,
but this actually matches nicely with GitLab auto-prefixing a 'v' on
https://gitlab.com/lilypond/lilypond/-/packages/5025866

signature.asc
Description: This is a digitally signed message part