On Wed, Mar 16, 2022 at 9:57 PM Jonas Hahnfeld via Discussions on
LilyPond development 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 versi
On Mar 16, 2022, at 17:04, Jean Abou Samra wrote:
>
> Le 16/03/2022 à 21:57, Jonas Hahnfeld via Discussions on LilyPond development
> a écrit :
>>
>>
...
>> would drop the superfluous "release/" prefix (probably still stemming
>> from CVS times?) and the "-1" suffix for the buildnumber, which
Le 16/03/2022 à 21:57, Jonas Hahnfeld via Discussions on LilyPond
development a écrit :
Hi all,
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
Hi all,
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:/
Le 19/02/2022 à 17:57, Jonas Hahnfeld a écrit :
Hi all,
I'd like to discuss what are considered blocker issues for a switch to
Guile 2.2.
After the release of 2.23.6, there were reports of major problems on
Windows, namely that the binaries were broken when extracted with the
Windows Explore
