Re: [release planning] GRASS GIS 8: create new release branch

--===============8086350871649200334==
Content-Type: multipart/alternative; boundary="0000000000000714ce05c4230a99"

--0000000000000714ce05c4230a99
Content-Type: text/plain; charset="UTF-8"

The word "branch" in "previewbranch_8_0" seems superfluous to me as it does
in releasebranch_7_8 plus it is two words together without a separator.
Would v8 be a good time to change that practice?

Advantages of just release_8_0:

A1) No 'branch == releasebranch_7_8' or 'switch to the releasebranch_7_8
branch' statements.

A2) Master branch is also only a branch and does not have the word branch
in it.

A3) Both QGIS and GDAL use only "release", not "branch", in the name of
their release branches.

Disadvantages of just release_8_0:

D1) In contexts where you use Git to get a specific branch or tag, you
don't see from the command that it is indeed a branch (in `git --branch
release_8_0`, release_8_0 could, in theory, be a tag). However, you are
likely to correctly guess it is a branch, not a tag, since tags for release
are most often mostly the numbers only, i.e., in format v8.0 or, as in our
case, 8.0.

D2) Scripts constructing the branch name from the version name will break,
however it seems like a better practice to me in this case to parameterize
the whole branch name and there needs to be likely other changes for v8 in
these scripts anyway.

Vaclav

On Sun, Jun 6, 2021 at 2:41 AM Markus Neteler <[email protected]> wrote:

> Hi all,
>
> The new 8.0.0alpha preview branch is ready:
>
> https://github.com/OSGeo/grass/tree/previewbranch_8_0
>
> Best,
> Markus
> _______________________________________________
> grass-dev mailing list
> [email protected]
> https://lists.osgeo.org/mailman/listinfo/grass-dev
>

--0000000000000714ce05c4230a99
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div>The word &quot;branch&quot; in &quot=
;previewbranch_8_0&quot; seems superfluous to me as it does in releasebranc=
h_7_8 plus it is two words together without a separator. Would v8 be a good=
 time to change that practice?</div><div><br></div><div>Advantages of just =
 release_8_0:</div><div><br></div><div>A1) No &#39;branch =3D=3D  releasebr=
anch_7_8&#39; or &#39;switch to the releasebranch_7_8 branch&#39; statement=
s.</div><div><br></div><div>A2) Master branch is also only a branch and doe=
s not have the word branch in it.</div><div><br></div><div>A3) Both QGIS an=
d GDAL use only &quot;release&quot;, not &quot;branch&quot;, in the name of=
 their release branches.<br></div></div><div><br></div><div>Disadvantages o=
f just  release_8_0:</div><div><br></div><div>D1) In contexts where you use=
 Git to get a specific branch or tag, you don&#39;t see from the command th=
at it is indeed a branch (in `git --branch release_8_0`, release_8_0 could,=
 in theory, be a tag). However, you are likely to correctly guess it is a b=
ranch, not a tag, since tags for release are most often mostly the numbers =
only, i.e., in format v8.0 or, as in our case, 8.0.<br></div><div><br></div=
><div>D2) Scripts constructing the branch name from the version name will b=
reak, however it seems like a better practice to me in this case to paramet=
erize the whole branch name and there needs to be likely other changes for =
v8 in these scripts anyway.</div><div><br></div><div>Vaclav<br></div><div><=
br></div><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">O=
n Sun, Jun 6, 2021 at 2:41 AM Markus Neteler &lt;<a href=3D"mailto:neteler@=
osgeo.org">[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex">Hi all,<br>
<br>
The new 8.0.0alpha preview branch is ready:<br>
<br>
<a href=3D"https://github.com/OSGeo/grass/tree/previewbranch_8_0" rel=3D"no=
referrer" target=3D"_blank">https://github.com/OSGeo/grass/tree/previewbran=
ch_8_0</a><br>
<br>
Best,<br>
Markus<br>
_______________________________________________<br>
grass-dev mailing list<br>
<a href=3D"mailto:[email protected]" target=3D"_blank">grass-dev@li=
sts.osgeo.org</a><br>
<a href=3D"https://lists.osgeo.org/mailman/listinfo/grass-dev" rel=3D"noref=
errer" target=3D"_blank">https://lists.osgeo.org/mailman/listinfo/grass-dev=
</a><br>
</blockquote></div></div>

--0000000000000714ce05c4230a99--

--===============8086350871649200334==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
grass-dev mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/grass-dev

--===============8086350871649200334==--