Hi all, Ok ... indeed it wasn't just creating a new branch and deleting the old ... there was lots of tooling blocking things. But now both our plc4x as well as our plc4x-build-tools repos are "master-free".
I also updated the website and the release documentation. Chris Am 03.07.20, 19:30 schrieb "Christofer Dutz" <[email protected]>: Ok, Just got the confirmation. I have to create the new branch, have infra unlock the old and then I can delete it. Chris ________________________________ Von: Christofer Dutz <[email protected]> Gesendet: Freitag, 3. Juli 2020 19:28 An: [email protected] <[email protected]> Betreff: Re: [RESULT] [VOTE] Rename our "master" branch to "release" I'm not sure there is no tooling from infra... ________________________________ Von: Julian Feinauer <[email protected]> Gesendet: Freitag, 3. Juli 2020 19:25 An: [email protected] <[email protected]> Betreff: Re: [RESULT] [VOTE] Rename our "master" branch to "release" Shouldn't rename or move do the trick? J Holen Sie sich Outlook für Android<https://aka.ms/ghei36> ________________________________ From: Christofer Dutz <[email protected]> Sent: Friday, July 3, 2020 6:19:25 PM To: [email protected] <[email protected]> Subject: [RESULT] [VOTE] Rename our "master" branch to "release" So the vote passes with 7 +1 votes (technically 5 binding and 2 non-binding) I'll try to find out if it's just creating a new branch and deleting the old and then take care od actually doing it. Chris Am 30.06.20, 16:00 schrieb "Otto Fowler" <[email protected]>: +1 because why not? Most others are considering “main” or something, avoiding what you are (I think) explicitly going for using release which as such meaning. Can always change it back On June 29, 2020 at 03:09:44, Christofer Dutz ([email protected]) wrote: Hi all, we had already discussed that some days ago, but I’d like to formally have you all vote on this … just to make it official. I always thought “master”, “trunk” etc. were sub-ideal names as they don’t explain what they are used for. We currently develop on “develop” and therefore I propose to change the “master” branch to “release”. While at it I would propose to call the release branches “release/x.y” (instead of “rel/x.y”) and to tag the releases themselves with the full three-digit numbers “release/x.y.z”). This way I think we would have all in a very clean and concise naming scheme where nobody has to ask himself, which branch is used for what. Chris
