[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: releasing 2.21.2

From: Jonas Hahnfeld
Subject: Re: releasing 2.21.2
Date: Sun, 21 Jun 2020 14:43:02 +0200
User-agent: Evolution 3.36.3

Am Sonntag, den 21.06.2020, 13:34 +0100 schrieb Phil Holmes:
> Looks like the tag command is hardwired in around line 185 of in 
> test-lily.

Ah, and the push command is right around the corner. I think the script
should just push it to both repositories:

diff --git a/test-lily/ b/test-lily/
index 4f1ba45c..9a86af84 100644
--- a/test-lily/
+++ b/test-lily/
@@ -185,10 +185,12 @@ def upload_binaries (repo, version, version_db):
     git_tag_cmd = 'git --git-dir %(git_dir)s tag -m "" -a %(git_tag)s 
%(dirred_branch)s' % locals ()
     my_maintainer_git_username = maintainer_git_username
     git_push_cmd = 'git --git-dir %(git_dir)s push 
refs/tags/%(git_tag)s:refs/tags/%(git_tag)s' % locals ()
+    git_push_cmd_gitlab = 'git --git-dir %(git_dir)s push 
refs/tags/%(git_tag)s:refs/tags/%(git_tag)s' % locals ()
     gub_tag_cmd = 'git tag -m "release of lilypond %(description)s 
(%(version_str)s-%(build)d)"  "gub-release-lilypond-%(version_str)s-%(build)d"' 
% locals ()
     cmds.append (git_tag_cmd)
     cmds.append (git_push_cmd)
+    cmds.append (git_push_cmd_gitlab)
     cmds.append (gub_tag_cmd)
     cmds.append ('make -f lilypond.make update-versions')

That's also what I would do for the existing tag release/2.21.2-1. No
need to do it from GUB though, just fetch it from Savannah and push it
to GitLab.


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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]