Re: [release planning] GRASS GIS 8: create new release branch
Veronica Andreo <[email protected]> Fri, 21 May 2021 16:01:53 +0200
| Newsgroups | gmane.comp.gis.grass.devel |
|---|---|
| Message-ID | <CAAMki4E+-qOxH7pyZZFXdAsXDVtC8Cgqa6ozD_M27YUAU-QP2g@mail.gmail.com> |
--===============8562683055631752427== Content-Type: multipart/alternative; boundary="0000000000002c6fa805c2d78168" --0000000000002c6fa805c2d78168 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi all, El jue, 20 may 2021 a las 17:21, Maris Nartiss (<[email protected]>) escribi=C3=B3: > Hello Makrus et al. > > 2021-05-15 16:40 GMT+03:00, Markus Neteler <[email protected]>: > > On Sat, May 15, 2021 at 4:05 AM Vaclav Petras <[email protected]> > wrote: > >> On Fri, May 14, 2021 at 11:10 AM Markus Neteler <[email protected]> > >> wrote: > >>> Let me suggest to create a new release branch in the next two weeks > >>> ... > >>> > >>> Now, the question is, also to avoid excessive cherry-picking of fixes > >>> and changes from master (to be called 8.1 then), which of the open PR > >>> may be merged soon? > > >> I actually expected that you would be a "beta" release, not an RC, > marked > >> by tagging a commit on master branch with the code as is. > >> This would avoid any backporting, > > > > Yes, that's an alternative idea. > > > >> but perhaps, it is not creating enough focus for 8.0 and having a 8.0 > >> branch gives more freedom in what goes into the master branch. > > > > Indeed, a full blown new release branch for G800 would open the master > > branch for new (radical) changes. > > > > @All: your opinion? > > I would like to get PR #1501 (depends on #1272) into master before > branching as it is already quite large and disruptive. > It is almost ready (today I wrote first of three management > functions). I want to finish lib part before merging =E2=80=93 management > module can be then created as a separate PR at some point later. > I'd really like to see these changes merged before the creation of grass 8 branch. Maybe we can agree on a deadline that suits both the need to have an 8 branch for the upcoming conferences where a GRASS 8 demo is already accepted (*FOSSGIS is in ~2 weeks*) and the time needed to complete ongoing development at least up to a working version that can be merged. @Maris Nartiss <[email protected]> what do you think? my 0.2 cents Vero --0000000000002c6fa805c2d78168 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr">Hi all, <br></div><br><div class=3D"gmail= _quote"><div dir=3D"ltr" class=3D"gmail_attr">El jue, 20 may 2021 a las 17:= 21, Maris Nartiss (<<a href=3D"mailto:[email protected]">maris.gis@gma= il.com</a>>) escribi=C3=B3:<br></div><blockquote class=3D"gmail_quote" s= tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad= ding-left:1ex">Hello Makrus et al.<br> <br> 2021-05-15 16:40 GMT+03:00, Markus Neteler <<a href=3D"mailto:neteler@os= geo.org" target=3D"_blank">[email protected]</a>>:<br> > On Sat, May 15, 2021 at 4:05 AM Vaclav Petras <<a href=3D"mailto:we= [email protected]" target=3D"_blank">[email protected]</a>> wrote:<b= r> >> On Fri, May 14, 2021 at 11:10 AM Markus Neteler <<a href=3D"mai= lto:[email protected]" target=3D"_blank">[email protected]</a>><br> >> wrote:<br> >>> Let me suggest to create a new release branch in the next two = weeks<br> >>> ...<br> >>><br> >>> Now, the question is, also to avoid excessive cherry-picking o= f fixes<br> >>> and changes from master (to be called 8.1 then), which of the = open PR<br> >>> may be merged soon?<br></blockquote><div>=C2=A0</div><blockquo= te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px = solid rgb(204,204,204);padding-left:1ex"> >> I actually expected that you would be a "beta" release, = not an RC, marked<br> >> by tagging a commit on master branch with the code as is.<br> >> This would avoid any backporting,<br> ><br> > Yes, that's an alternative idea.<br> ><br> >> but perhaps, it is not creating enough focus for 8.0 and having a = 8.0<br> >> branch gives more freedom in what goes into the master branch.<br> ><br> > Indeed, a full blown new release branch for G800 would open the master= <br> > branch for new (radical) changes.<br> ><br> > @All: your opinion?<br> <br> I would like to get PR #1501 (depends on #1272) into master before<br> branching as it is already quite large and disruptive.<br> It is almost ready (today I wrote first of three management<br> functions). I want to finish lib part before merging =E2=80=93 management<b= r> module can be then created as a separate PR at some point later.<br></block= quote><div><br></div><div>I'd really like to see these changes merged b= efore the creation of grass 8=C2=A0 branch. <br></div><div><br></div><div>M= aybe we can agree on a deadline that suits both the need to have an 8 branc= h for the upcoming conferences where a GRASS 8 demo is already accepted (<b= >FOSSGIS is in ~2 weeks</b>) and the time needed to complete ongoing develo= pment at least up to a working version that can be merged. <br></div><div><= br></div><div><a class=3D"gmail_plusreply" id=3D"plusReplyChip-0" href=3D"m= ailto:[email protected]" tabindex=3D"-1">@Maris Nartiss</a> what do you t= hink?</div><div><br></div><div>my 0.2 cents</div><div>Vero<br></div></div><= div class=3D"gmail_quote"><br></div></div> --0000000000002c6fa805c2d78168-- --===============8562683055631752427== 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 --===============8562683055631752427==--