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

--===============7380247179579435595==
Content-Type: multipart/alternative; boundary="000000000000c23f8b05c4bb4c19"

--000000000000c23f8b05c4bb4c19
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Maris,

El mi=C3=A9, 9 jun 2021 a las 9:23, Maris Nartiss (<[email protected]>)
escribi=C3=B3:

> Hello Veronica,
> thanks for pushing this forward.
>
> Looking from a "it is ready when it is ready" perspective =E2=80=93 what =
we
> are missing from functionality to call 8.0 ready? (I mean only things
> that are expected to be ready in less than a month)
>

I think, others please correct me if I'm wrong, restructuring the add-ons
repo + adapting g.extension are the main things missing/to be finished.


> From my side:
> Band references and integration with signature files are ready to be
> merged (please review!), missing functionality can wait for 8.2.
> https://github.com/OSGeo/grass/pull/1272
> https://github.com/OSGeo/grass/pull/1501
>
> I'll try to work on r.in.pdal this Friday (I need to do some LiDAR
> work myself). It is almost merge ready (as long as we add extra
> functionality in 8.2)
> https://github.com/OSGeo/grass/pull/1200
>
> Then from my side I'd call 8.0 ready.
>

Great!!

So, can we have a birthday release then? :-D

Vero

2021-06-08 17:09 GMT+03:00, Veronica Andreo <[email protected]>:
> > 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 FOSS4=
G,
> > say August for example?
> >
> > I think it's really important to agree on a date so we can all manage o=
ur
> > reduced time and focus our efforts towards that aim.
> > What do you say?
> >
> > Best,
> > Vero
>

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

<div dir=3D"ltr"><div>Hi Maris,<br></div><br><div class=3D"gmail_quote"><di=
v dir=3D"ltr" class=3D"gmail_attr">El mi=C3=A9, 9 jun 2021 a las 9:23, Mari=
s Nartiss (&lt;<a href=3D"mailto:[email protected]">[email protected]</=
a>&gt;) escribi=C3=B3:<br></div><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-lef=
t:1ex">Hello Veronica,<br>
thanks for pushing this forward.<br>
<br>
Looking from a &quot;it is ready when it is ready&quot; perspective =E2=80=
=93 what we<br>
are missing from functionality to call 8.0 ready? (I mean only things<br>
that are expected to be ready in less than a month)<br></blockquote><div><b=
r></div><div>I think, others please correct me if I&#39;m wrong,  restructu=
ring the add-ons repo=C2=A0+ adapting g.extension are the main things missi=
ng/to be finished. <br></div><div>=C2=A0</div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,20=
4);padding-left:1ex">
From my side:<br>
Band references and integration with signature files are ready to be<br>
merged (please review!), missing functionality can wait for 8.2.<br>
<a href=3D"https://github.com/OSGeo/grass/pull/1272" rel=3D"noreferrer" tar=
get=3D"_blank">https://github.com/OSGeo/grass/pull/1272</a><br>
<a href=3D"https://github.com/OSGeo/grass/pull/1501" rel=3D"noreferrer" tar=
get=3D"_blank">https://github.com/OSGeo/grass/pull/1501</a><br>
<br>
I&#39;ll try to work on r.in.pdal this Friday (I need to do some LiDAR<br>
work myself). It is almost merge ready (as long as we add extra<br>
functionality in 8.2)<br>
<a href=3D"https://github.com/OSGeo/grass/pull/1200" rel=3D"noreferrer" tar=
get=3D"_blank">https://github.com/OSGeo/grass/pull/1200</a><br>
<br>
Then from my side I&#39;d call 8.0 ready.<br></blockquote><div><br></div><d=
iv>Great!! <br></div><div><br></div><div>So, can we have a birthday release=
 then? :-D<br></div><div><br></div><div>Vero<br></div><div><br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex">

2021-06-08 17:09 GMT+03:00, Veronica Andreo &lt;<a href=3D"mailto:veroandre=
[email protected]" target=3D"_blank">[email protected]</a>&gt;:<br>
&gt; Hello devs,<br>
&gt;<br>
&gt; As you all know, grass birthday is approaching... July 29th is just ar=
ound<br>
&gt; the corner. I&#39;d love to celebrate GRASS&#39; bday with a new relea=
se, with a<br>
&gt; big release ;)<br>
&gt; Do you think that is doable? How much is missing for GRASS 8 release?<=
br>
&gt;<br>
&gt; The next important date is FOSS4G 2021 on September 27th - October 2nd=
,<br>
&gt; where we have proposed GRASS 8 talks and workshops. If we can&#39;t ma=
ke it for<br>
&gt; GRASS GIS&#39; birthday, do you think it&#39;s feasible to release bef=
ore FOSS4G,<br>
&gt; say August for example?<br>
&gt;<br>
&gt; I think it&#39;s really important to agree on a date so we can all man=
age our<br>
&gt; reduced time and focus our efforts towards that aim.<br>
&gt; What do you say?<br>
&gt;<br>
&gt; Best,<br>
&gt; Vero<br>
</blockquote></div></div>

--000000000000c23f8b05c4bb4c19--

--===============7380247179579435595==
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

--===============7380247179579435595==--