Re: releasing 2.21.2

[Jonas Hahnfeld]

Am Sonntag, den 21.06.2020, 13:34 +0100 schrieb Phil Holmes:
> Looks like the tag command is hardwired in around line 185 of upload.py 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/upload.py b/test-lily/upload.py
index 4f1ba45c..9a86af84 100644
--- a/test-lily/upload.py
+++ b/test-lily/upload.py
@@ -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 
ssh+git://%(my_maintainer_git_username)s@git.sv.gnu.org/srv/git/lilypond.git/ 
refs/tags/%(git_tag)s:refs/tags/%(git_tag)s' % locals ()
+    git_push_cmd_gitlab = 'git --git-dir %(git_dir)s push 
git@gitlab.com:lilypond/lilypond.git 
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.

Jonas

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