- Original Message -
From: "Federico Bruni"
To: "Jonas Hahnfeld"
Cc: "Phil Holmes" ; "lilypond-devel"
Sent: Sunday, June 21, 2020 3:05 PM
Subject: Re: releasing 2.21.2
Phil, while rebasing a local branch I noticed that you forgot
Phil, while rebasing a local branch I noticed that you forgot to bump
the latest version here:
https://gitlab.com/lilypond/lilypond/-/blob/master/Documentation/web/news-headlines.itexi#L23
should be 2.21.2
BTW, the anchors for the @uref items in news-headlines.itexi are giving
me headache
Am Sonntag, den 21.06.2020, 14:45 +0200 schrieb Jonas Hahnfeld:
> Am Sonntag, den 21.06.2020, 13:42 +0100 schrieb Phil Holmes:
> > Merge request added. GitLab automatically added the labels Patch New.
> > Does
> > that need changing to get it into master?
>
> No, you can ignore the label becau
Am Sonntag, den 21.06.2020, 13:42 +0100 schrieb Phil Holmes:
> Merge request added. GitLab automatically added the labels Patch New. Does
> that need changing to get it into master?
No, you can ignore the label because you're not actually after review
for that one. Just hit "Merge when pipeline
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.p
Merge request added. GitLab automatically added the labels Patch New. Does
that need changing to get it into master?
--
Phil Holmes
- Original Message -
From: "Jonas Hahnfeld"
To: "Phil Holmes" ; "lilypond-devel"
Sent: Sunday, June 21, 2020 1:02 PM
Subject: Re: releasing 2.21.2
Looks like the tag command is hardwired in around line 185 of upload.py in
test-lily.
--
Phil Holmes
- Original Message -
From: "Jonas Hahnfeld"
To: "Phil Holmes" ; "lilypond-devel"
Sent: Sunday, June 21, 2020 1:02 PM
Subject: Re: releasing 2.21.2
Am Sonntag, den 21.06.2020, 12:53 +0100 schrieb Phil Holmes:
> Just successfully built and uploaded GUB :-)
Awesome!
> Two further questions:
>
> 1. Is there any problem with doing the final file updates (i.e. VERSION)
> into release/unstable and then opening a merge request from this branch?
this be a manual step now?
--
Phil Holmes
- Original Message -
From: "Jonas Hahnfeld"
To: "Phil Holmes" ; "lilypond-devel"
Sent: Sunday, June 21, 2020 11:21 AM
Subject: Re: releasing 2.21.2
Am Sonntag, den 21.06.2020, 11:14 +0100 schrieb Phil Holmes:
> Just checking here. The process for pushing to release/unstable hasn't
> changed when using GitLab?
No change, just push as you did for Savannah. Force-pushes are
prevented, but that shouldn't pose a problem.
> What about synchronis
s" ; "lilypond-devel"
Sent: Saturday, June 20, 2020 2:01 PM
Subject: Re: releasing 2.21.2
On Sat, Jun 20, 2020 at 3:01 PM Jonas Hahnfeld wrote:
>
> Am Samstag, den 20.06.2020, 13:55 +0100 schrieb Phil Holmes:
> > OK. First question. Should I switch completely to GitLab for doing all the
> > updating of news, VERSION, etc? That is - pretty much stop using Savannah
> > for anything ex
;lilypond-devel"
Cc:
Sent: Friday, June 19, 2020 8:05 PM
Subject: Re: releasing 2.21.2
Am Samstag, den 20.06.2020, 13:55 +0100 schrieb Phil Holmes:
> OK. First question. Should I switch completely to GitLab for doing all the
> updating of news, VERSION, etc? That is - pretty much stop using Savannah
> for anything except GUB builds using my GUB user.
Yes, that would be best. If
Am Donnerstag, den 11.06.2020, 16:12 +0200 schrieb Jonas Hahnfeld:
> Hi all,
>
> with an initial CG update for GitLab committed, I'd like to propose
> that we have our next unstable release 2.21.2 to get the documentation
> available online.
>
> Due to the problems we had in the past, I decided t
Hi all,
with an initial CG update for GitLab committed, I'd like to propose
that we have our next unstable release 2.21.2 to get the documentation
available online.
Due to the problems we had in the past, I decided to test GUB before
Phil runs into problems. It took no less than 4 commits to make
16 matches
Mail list logo
