You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@plc4x.apache.org by Christofer Dutz <ch...@c-ware.de> on 2020/06/29 07:09:33 UTC
[VOTE] Rename our "master" branch to "release"
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
Re: [VOTE] Rename our "master" branch to "release"
Posted by Julian Feinauer <j....@pragmaticminds.de>.
+1
Julian
Am 29.06.20, 09:09 schrieb "Christofer Dutz" <ch...@c-ware.de>:
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
Re: [VOTE] Rename our "master" branch to "release"
Posted by Cesar Garcia <ce...@ceos.com.ve>.
1+
El lun., 29 jun. 2020 a las 3:09, Christofer Dutz (<
christofer.dutz@c-ware.de>) escribió:
> 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
>
>
>
--
*CEOS Automatización, C.A.*
*GALPON SERVICIO INDUSTRIALES Y NAVALES FA, C.A.,*
*PISO 1, OFICINA 2, AV. RAUL LEONI, SECTOR GUAMACHITO,*
*FRENTE A LA ASOCIACION DE GANADEROS,BARCELONA,EDO. ANZOATEGUI*
*Ing. César García*
*Cel: +58 414-760.98.95*
*Hotline Técnica SIEMENS: 0800 1005080*
*Email: support.aan.automation@siemens.com
<su...@siemens.com>*
Re: [VOTE] Rename our "master" branch to "release"
Posted by Sebastian Rühl <se...@googlemail.com.INVALID>.
+1
Sebastian
> Am 29.06.2020 um 09:09 schrieb Christofer Dutz <ch...@c-ware.de>:
>
> 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
>
>
Re: [VOTE] Rename our "master" branch to "release"
Posted by Justin Mclean <ju...@classsoftware.com>.
+1 a much better description of that branch
Re: [VOTE] Rename our "master" branch to "release"
Posted by Lukas Ott <ot...@gmail.com>.
+1
Lukas
Am Mo., 29. Juni 2020 um 09:10 Uhr schrieb Christofer Dutz <
christofer.dutz@c-ware.de>:
> +1 (binding)
>
> Chris
>
>
> Am 29.06.20, 09:09 schrieb "Christofer Dutz" <ch...@c-ware.de>:
>
> 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
>
>
>
>
Re: [VOTE] Rename our "master" branch to "release"
Posted by Christofer Dutz <ch...@c-ware.de>.
+1 (binding)
Chris
Am 29.06.20, 09:09 schrieb "Christofer Dutz" <ch...@c-ware.de>:
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
Re: [VOTE] Rename our "master" branch to "release"
Posted by Otto Fowler <ot...@gmail.com>.
+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 (christofer.dutz@c-ware.de)
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