Re: [release planning] GRASS GIS 8: create new release branch
Veronica Andreo <[email protected]> Tue, 8 Jun 2021 16:09:54 +0200
| Newsgroups | gmane.comp.gis.grass.devel |
|---|---|
| Message-ID | <CAAMki4FTJa0bdVaNs_Ak3i74UFy76TfpTw4fRX=W1M5s+FMkZQ@mail.gmail.com> |
--===============7297114687216592752== Content-Type: multipart/alternative; boundary="000000000000f7a08b05c441b672" --000000000000f7a08b05c441b672 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello devs, As you all know, grass birthday is approaching... July 29th is just around the corner. I'd love to celebrate GRASS' bday with a new release, with a big release ;) Do you think that is doable? How much is missing for GRASS 8 release? The next important date is FOSS4G 2021 on September 27th - October 2nd, where we have proposed GRASS 8 talks and workshops. If we can't make it for GRASS GIS' birthday, do you think it's feasible to release before FOSS4G, say August for example? I think it's really important to agree on a date so we can all manage our reduced time and focus our efforts towards that aim. What do you say? Best, Vero El lun, 7 jun 2021 a las 3:34, Vaclav Petras (<[email protected]>) escribi=C3=B3: > 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 =3D=3D 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 relea= se > are most often mostly the numbers only, i.e., in format v8.0 or, as in ou= r > 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 parameteriz= e > the whole branch name and there needs to be likely other changes for v8 i= n > 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 >> > _______________________________________________ > grass-dev mailing list > [email protected] > https://lists.osgeo.org/mailman/listinfo/grass-dev > --000000000000f7a08b05c441b672 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>Hello devs, <br></div><div><br></div><div>As you all = know, grass birthday is approaching... July 29th is just around the corner.= I'd love to celebrate GRASS' bday with a new release, with a big r= elease ;) <br></div><div>Do you think that is doable? How much is missing f= or GRASS 8 release?<br></div><div><br></div><div>The next important date is= FOSS4G 2021 on September 27th - October 2nd, where we have proposed GRASS = 8 talks and workshops. If we can't make it for GRASS GIS' birthday,= do you think it's feasible to release before FOSS4G, say August for ex= ample?</div><div><br></div><div>I think it's really important to agree = on a date so we can all manage our reduced time and focus our efforts towar= ds that aim. <br></div><div>What do you say?</div><div><br></div><div>Best,= <br></div><div>Vero<br></div></div><br><div class=3D"gmail_quote"><div dir= =3D"ltr" class=3D"gmail_attr">El lun, 7 jun 2021 a las 3:34, Vaclav Petras = (<<a href=3D"mailto:[email protected]">[email protected]</a>>) = escribi=C3=B3:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0= px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><= div dir=3D"ltr"><div dir=3D"ltr"><div>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?</div><div><br></div><div>Advantages of just = release_8_0:</div><div><br></div><div>A1) No 'branch =3D=3D releasebra= nch_7_8' or 'switch to the releasebranch_7_8 branch' statements= .</div><div><br></div><div>A2) Master branch is also only a branch and does= not have the word branch in it.</div><div><br></div><div>A3) Both QGIS and= GDAL use only "release", not "branch", in the name of = their release branches.<br></div></div><div><br></div><div>Disadvantages of= 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't see from the command tha= t 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 br= anch, not a tag, since tags for release are most often mostly the numbers o= nly, 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 br= eak, however it seems like a better practice to me in this case to paramete= rize the whole branch name and there needs to be likely other changes for v= 8 in these scripts anyway.</div><div><br></div><div>Vaclav<br></div><div><b= r></div><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On= Sun, Jun 6, 2021 at 2:41 AM Markus Neteler <<a href=3D"mailto:neteler@o= sgeo.org" target=3D"_blank">[email protected]</a>> wrote:<br></div><bloc= kquote class=3D"gmail_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> _______________________________________________<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> --000000000000f7a08b05c441b672-- --===============7297114687216592752== 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 --===============7297114687216592752==--