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

[Moritz Lennert]

Le 16 août 2021 18:20:42 GMT+02:00, Veronica Andreo  a 
écrit :
>Hi all,
>
>El vie, 6 ago 2021 a las 4:29, Vaclav Petras ()
>escribió:
>
>> Are we ready to create the 8.0 release branch?
>>
>
>Seems we are!!
>
>Once we create it, we will need to backport (cherry-pick) updates from the
>> master branch when needed.
>>
>> Please see the following for the individual issues we still have and post
>> here if you see some priorities.
>>
>> On Wed, Jul 14, 2021 at 5:24 PM Vaclav Petras 
>> wrote:
>>
>>>
>>>
 Windows build & test is just bad (no bug or PR so far?),
>>>
>>>
>>> Can someone give an update on that, please?
>>>
>>
>>
>>> #1683 is not merged yet, but missing sh in the test environment is not a
>>> blocker in this case.
>>>
>>
>> https://github.com/OSGeo/grass/pull/1683
>>
>> Tests are running!
>>
>>
>>>  CentOS is too
>>>
 old (#1709) & needs auto tools update to fix it (or at least env
 variable in build script as I just have done to enable testing in
 #1501),
>>>
>>>
>>> ...or CentOS 8, CentOS Stream, or remove the CentOS test.
>>>
>>> https://github.com/OSGeo/grass/issues/1709#issuecomment-880215427
>>>
>>
>> It would be better if Autotools are updated, but CentOS build works now.
>> Are there any pressing issues?
>>
>>
>>> I would also strongly advocate merging ctypes upgrade before 8.0

>>>
>>> Seems to be close to being finished too.
>>>
>>
>> ctypes update is closer everyday, but not finished yet. Maybe not needed
>> for 8.0?
>>
>> https://github.com/OSGeo/grass/pull/1651
>>
>
>Milestone was changed to 8.2 and Nicklas suggest to move forward with
>release branch 8
>
>>
>> On Wed, Jul 28, 2021 at 4:28 AM Maris Nartiss  wrote:
>>
>>> 2021-07-27 18:26 GMT+03:00, Vaclav Petras :
>>> >
>>> > From what has the milestone 8.0 and is not mentioned below and is
>>> major, I
>>> > see only #1454 and #1501 which are related to band references. Maybe we
>>> > should again consider reverting the band references in order to get 8.0
>>> out
>>> > or how do you see the status of #1454 and #1501, Martin and Maris?
>>> >
>>> > https://github.com/OSGeo/grass/milestone/4
>>> > https://github.com/OSGeo/grass/pull/1454
>>> > https://github.com/OSGeo/grass/pull/1501
>>>
>>> For #1454 the main remaining (and unsolvable) issue is semantics of a
>>> mapset layout and its management functions. I just commited a more
>>> clean workaround and thus it should be ready for a merge. A proper
>>> solution will have to wait for GRASS 9 when we could reorganize mapset
>>> structure and thus also clean-up naming, handling functions etc.
>>>
>>
>> #1501 (Integrate band references into portable signature files) is close
>> to being merged.
>>
>
>this one was merged just after you posted this
>
>#1454 (TGIS DB v3 backward compatible with v2) has perhaps lower priority
>> since there is both upgrade and downgrade.
>>
>> As for issues linked to the milestone, please review what is there. See
>> what needs to stay there and what can be moved. For example, all issues
>> which are features and are not changing existing API can be moved to 8.2
>> milestone.
>>
>> https://github.com/OSGeo/grass/milestone/4
>>
>
> If no further objections I'd suggest to move forward with grass8 release
>branch creation

+1

Moritz
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Veronica Andreo]

Hi all,

El vie, 6 ago 2021 a las 4:29, Vaclav Petras ()
escribió:

> Are we ready to create the 8.0 release branch?
>

Seems we are!!

Once we create it, we will need to backport (cherry-pick) updates from the
> master branch when needed.
>
> Please see the following for the individual issues we still have and post
> here if you see some priorities.
>
> On Wed, Jul 14, 2021 at 5:24 PM Vaclav Petras 
> wrote:
>
>>
>>
>>> Windows build & test is just bad (no bug or PR so far?),
>>
>>
>> Can someone give an update on that, please?
>>
>
>
>> #1683 is not merged yet, but missing sh in the test environment is not a
>> blocker in this case.
>>
>
> https://github.com/OSGeo/grass/pull/1683
>
> Tests are running!
>
>
>>  CentOS is too
>>
>>> old (#1709) & needs auto tools update to fix it (or at least env
>>> variable in build script as I just have done to enable testing in
>>> #1501),
>>
>>
>> ...or CentOS 8, CentOS Stream, or remove the CentOS test.
>>
>> https://github.com/OSGeo/grass/issues/1709#issuecomment-880215427
>>
>
> It would be better if Autotools are updated, but CentOS build works now.
> Are there any pressing issues?
>
>
>> I would also strongly advocate merging ctypes upgrade before 8.0
>>>
>>
>> Seems to be close to being finished too.
>>
>
> ctypes update is closer everyday, but not finished yet. Maybe not needed
> for 8.0?
>
> https://github.com/OSGeo/grass/pull/1651
>

Milestone was changed to 8.2 and Nicklas suggest to move forward with
release branch 8

>
> On Wed, Jul 28, 2021 at 4:28 AM Maris Nartiss  wrote:
>
>> 2021-07-27 18:26 GMT+03:00, Vaclav Petras :
>> >
>> > From what has the milestone 8.0 and is not mentioned below and is
>> major, I
>> > see only #1454 and #1501 which are related to band references. Maybe we
>> > should again consider reverting the band references in order to get 8.0
>> out
>> > or how do you see the status of #1454 and #1501, Martin and Maris?
>> >
>> > https://github.com/OSGeo/grass/milestone/4
>> > https://github.com/OSGeo/grass/pull/1454
>> > https://github.com/OSGeo/grass/pull/1501
>>
>> For #1454 the main remaining (and unsolvable) issue is semantics of a
>> mapset layout and its management functions. I just commited a more
>> clean workaround and thus it should be ready for a merge. A proper
>> solution will have to wait for GRASS 9 when we could reorganize mapset
>> structure and thus also clean-up naming, handling functions etc.
>>
>
> #1501 (Integrate band references into portable signature files) is close
> to being merged.
>

this one was merged just after you posted this

#1454 (TGIS DB v3 backward compatible with v2) has perhaps lower priority
> since there is both upgrade and downgrade.
>
> As for issues linked to the milestone, please review what is there. See
> what needs to stay there and what can be moved. For example, all issues
> which are features and are not changing existing API can be moved to 8.2
> milestone.
>
> https://github.com/OSGeo/grass/milestone/4
>

 If no further objections I'd suggest to move forward with grass8 release
branch creation

Best,
Vero
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Vaclav Petras]

Are we ready to create the 8.0 release branch?

Once we create it, we will need to backport (cherry-pick) updates from the
master branch when needed.

Please see the following for the individual issues we still have and post
here if you see some priorities.

On Wed, Jul 14, 2021 at 5:24 PM Vaclav Petras  wrote:

>
>
>
>> Windows build & test is just bad (no bug or PR so far?),
>
>
> Can someone give an update on that, please?
>


> #1683 is not merged yet, but missing sh in the test environment is not a
> blocker in this case.
>

https://github.com/OSGeo/grass/pull/1683

Tests are running!


>  CentOS is too
>
>> old (#1709) & needs auto tools update to fix it (or at least env
>> variable in build script as I just have done to enable testing in
>> #1501),
>
>
> ...or CentOS 8, CentOS Stream, or remove the CentOS test.
>
> https://github.com/OSGeo/grass/issues/1709#issuecomment-880215427
>

It would be better if Autotools are updated, but CentOS build works now.
Are there any pressing issues?

>
>
>> I would also strongly advocate merging ctypes upgrade before 8.0
>>
>
> Seems to be close to being finished too.
>

ctypes update is closer everyday, but not finished yet. Maybe not needed
for 8.0?

https://github.com/OSGeo/grass/pull/1651

On Wed, Jul 28, 2021 at 4:28 AM Maris Nartiss  wrote:

> 2021-07-27 18:26 GMT+03:00, Vaclav Petras :
> >
> > From what has the milestone 8.0 and is not mentioned below and is major,
> I
> > see only #1454 and #1501 which are related to band references. Maybe we
> > should again consider reverting the band references in order to get 8.0
> out
> > or how do you see the status of #1454 and #1501, Martin and Maris?
> >
> > https://github.com/OSGeo/grass/milestone/4
> > https://github.com/OSGeo/grass/pull/1454
> > https://github.com/OSGeo/grass/pull/1501
> >
>
> For #1454 the main remaining (and unsolvable) issue is semantics of a
> mapset layout and its management functions. I just commited a more
> clean workaround and thus it should be ready for a merge. A proper
> solution will have to wait for GRASS 9 when we could reorganize mapset
> structure and thus also clean-up naming, handling functions etc.
>

#1501 (Integrate band references into portable signature files) is close to
being merged.

#1454 (TGIS DB v3 backward compatible with v2) has perhaps lower priority
since there is both upgrade and downgrade.

As for issues linked to the milestone, please review what is there. See
what needs to stay there and what can be moved. For example, all issues
which are features and are not changing existing API can be moved to 8.2
milestone.

https://github.com/OSGeo/grass/milestone/4
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Maris Nartiss]

2021-07-27 18:26 GMT+03:00, Vaclav Petras :
>
> From what has the milestone 8.0 and is not mentioned below and is major, I
> see only #1454 and #1501 which are related to band references. Maybe we
> should again consider reverting the band references in order to get 8.0 out
> or how do you see the status of #1454 and #1501, Martin and Maris?
>
> https://github.com/OSGeo/grass/milestone/4
> https://github.com/OSGeo/grass/pull/1454
> https://github.com/OSGeo/grass/pull/1501
>

For #1454 the main remaining (and unsolvable) issue is semantics of a
mapset layout and its management functions. I just commited a more
clean workaround and thus it should be ready for a merge. A proper
solution will have to wait for GRASS 9 when we could reorganize mapset
structure and thus also clean-up naming, handling functions etc.

Māris.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Vaclav Petras]

On Tue, 8 Jun 2021 at 16:10, Veronica Andreo  wrote:

> As you all know, grass birthday is approaching... July 29th is just
around the corner.

I would say the master branch looks good in terms of fixes versus
potentially breaking commits (grass.jupyter and grass.benchmark will both
be marked as experimental in the release (grass.benchmark already is),
possibly not even advertised):

https://github.com/OSGeo/grass/commits/master

Perhaps a good time to create the release branch for 8.0? Opinions?

>From what has the milestone 8.0 and is not mentioned below and is major, I
see only #1454 and #1501 which are related to band references. Maybe we
should again consider reverting the band references in order to get 8.0 out
or how do you see the status of #1454 and #1501, Martin and Maris?

https://github.com/OSGeo/grass/milestone/4
https://github.com/OSGeo/grass/pull/1454
https://github.com/OSGeo/grass/pull/1501

See the status of what was discussed in this thread below.

On Wed, Jul 14, 2021 at 5:24 PM Vaclav Petras  wrote:

>
>
> On Sat, Jul 10, 2021 at 4:20 AM Maris Nartiss  wrote:
>
>> Hello all.
>>
>> 2021-07-09 21:39 GMT+03:00, Markus Neteler :
>>
>> > So, from my point of view, as you suggest:
>> >
>> > - get g.extension working, then
>>
>
> #1700 seems to be close to being finished. Please test.
>
> https://github.com/OSGeo/grass/pull/1700
>

Merged by Stefan Blumentrath 6 days ago. Seems to be working well.


>
>
>> There are a few PRs to merge but they are stuck due to failing tests –
>>
>
> I fixed the g.download.location part in #1715 and all or most "randomly"
> failing tests in #1681.
>
> https://github.com/OSGeo/grass/pull/1681
>

Both of these seem to be stable as well.


>
>
>> Windows build & test is just bad (no bug or PR so far?),
>
>
> Can someone give an update on that, please?
>

#1683 is not merged yet, but missing sh in the test environment is not a
blocker in this case.

https://github.com/OSGeo/grass/pull/1683


>
>
>> CentOS is too
>> old (#1709) & needs auto tools update to fix it (or at least env
>> variable in build script as I just have done to enable testing in
>> #1501),
>
>
> ...or CentOS 8, CentOS Stream, or remove the CentOS test.
>
> https://github.com/OSGeo/grass/issues/1709#issuecomment-880215427
>

The CI now contains environmental settings which are applicable to users
using older systems with old compilers. It would be better if it is
automatic, but it works now.

>
>
>
>> Ubuntu based test scripts use g.download.location extension
>> that is not operational at the moment (fixed by #1715?).
>>
>
> #1715 is merged, so the tests are fixed.
>
>
>>
>> I would also strongly advocate merging ctypes upgrade before 8.0
>>
>
> Seems to be close to being finished too.
>

Closer, but not quite finished yet. The not working piece seems to be just
the unusual use of NULL as a value for RASTER3D_DEFAULT_WINDOW.

https://github.com/OSGeo/grass/pull/1651

Best,
Vaclav
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Vaclav Petras]

On Sat, Jul 10, 2021 at 4:20 AM Maris Nartiss  wrote:

> Hello all.
>
> 2021-07-09 21:39 GMT+03:00, Markus Neteler :
> > Hi Anna, all,
>
> > So, from my point of view, as you suggest:
> >
> > - get g.extension working, then
>

#1700 seems to be close to being finished. Please test.

https://github.com/OSGeo/grass/pull/1700


> There are a few PRs to merge but they are stuck due to failing tests –
>

I fixed the g.download.location part in #1715 and all or most "randomly"
failing tests in #1681.

https://github.com/OSGeo/grass/pull/1681


> Windows build & test is just bad (no bug or PR so far?),


Can someone give an update on that, please?


> CentOS is too
> old (#1709) & needs auto tools update to fix it (or at least env
> variable in build script as I just have done to enable testing in
> #1501),


...or CentOS 8, CentOS Stream, or remove the CentOS test.

https://github.com/OSGeo/grass/issues/1709#issuecomment-880215427


> Ubuntu based test scripts use g.download.location extension
> that is not operational at the moment (fixed by #1715?).
>

#1715 is merged, so the tests are fixed.


>
> I would also strongly advocate merging ctypes upgrade before 8.0
>

Seems to be close to being finished too.

Vaclav


>
> > Best,
> > Markus
>
> Māris.
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Maris Nartiss]

Hello all.

2021-07-09 21:39 GMT+03:00, Markus Neteler :
> Hi Anna, all,

> So, from my point of view, as you suggest:
>
> - get g.extension working, then
> - create a new release branch
> - after that the GSoC merge into master.

There are a few PRs to merge but they are stuck due to failing tests –
Windows build & test is just bad (no bug or PR so far?), CentOS is too
old (#1709) & needs auto tools update to fix it (or at least env
variable in build script as I just have done to enable testing in
#1501), Ubuntu based test scripts use g.download.location extension
that is not operational at the moment (fixed by #1715?).

I would also strongly advocate merging ctypes upgrade before 8.0

> Best,
> Markus

Māris.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Vaclav Petras]

On Fri, Jul 9, 2021 at 2:40 PM Markus Neteler  wrote:

>
> PS wer could even rename "master" to "main" soon
>

+1 from me. GitHub supports the rename nicely. It modifies open PRs
automatically and gives messages to every user who opens the repo page,
although I really tried that only for a single repo case, not a
upstream-fork case. Anyway, this should be easier than the version branch
system switch in addons.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Markus Neteler]

Hi Anna, all,

Anna Petrášová  schrieb am Fr., 9. Juli 2021, 16:43:

> Hi Markus and all,
>
> was there a plan to release G8 from the previewbranch or are we branching
> out? I am fine with either, we can always cherrypick the fixes since
> branching previewbranch. I would like to soon merge changes from GSoC that
> shouldn't go into release. We could also wait for the g.extension fixes and
> then create the branch to minimize work.
>

I'd do the latter since we had so many changes that cherry picking is too
much work.

So, from my point of view, as you suggest:

- get g.extension working, then
- create a new release branch
- after that the GSoC merge into master.


Best,
Markus

PS wer could even rename "master" to "main" soon
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Anna Petrášová]

Hi Markus and all,

was there a plan to release G8 from the previewbranch or are we branching
out? I am fine with either, we can always cherrypick the fixes since
branching previewbranch. I would like to soon merge changes from GSoC that
shouldn't go into release. We could also wait for the g.extension fixes and
then create the branch to minimize work.

Anna

On Sun, Jun 6, 2021 at 2:41 AM Markus Neteler  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
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Luca Delucchi]

Il lun 14 giu 2021, 16:38 Veronica Andreo  ha scritto:

> Ciao Luca,
>

Ciao Vero,

>
>
> This is great news! It'd be great to have t.remove flags behaviour
> changed/fixed in grass 8.
> Shall we move the ticket in trac to an issue in github so we give it more
> visibility? If yes, I can do that.
>

For me it is not needed, if you like to move it I'm not against.

>
>
> cheers,
> Vero
>

Ciao
Luca

>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Veronica Andreo]

Hi Maris,

El mié, 9 jun 2021 a las 9:23, Maris Nartiss ()
escribió:

> Hello Veronica,
> thanks for pushing this forward.
>
> Looking from a "it is ready when it is ready" perspective – 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 :
> > 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
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Veronica Andreo]

Ciao Luca,

El vie, 11 jun 2021 a las 12:40, Luca Delucchi ()
escribió:

> On Tue, 8 Jun 2021 at 16:10, Veronica Andreo  wrote:
> > Hello devs,
>
> Hi,
>
> > 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?
>
> I would like to improve t.remove as reported
> https://trac.osgeo.org/grass/ticket/3362#comment:1
> I try to work on it next week
>

This is great news! It'd be great to have t.remove flags behaviour
changed/fixed in grass 8.
Shall we move the ticket in trac to an issue in github so we give it more
visibility? If yes, I can do that.

cheers,
Vero
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Luca Delucchi]

On Tue, 8 Jun 2021 at 16:10, Veronica Andreo  wrote:
>
> Hello devs,
>

Hi,

> 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?
>

I would like to improve t.remove as reported
https://trac.osgeo.org/grass/ticket/3362#comment:1
I try to work on it next week

>
> Best,
> Vero
>


-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Maris Nartiss]

Hello Veronica,
thanks for pushing this forward.

Looking from a "it is ready when it is ready" perspective – 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)

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.
Māris.



2021-06-08 17:09 GMT+03:00, Veronica Andreo :
> 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
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Veronica Andreo]

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 ()
escribió:

> 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  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
>> grass-dev@lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/grass-dev
>>
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Vaclav Petras]

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  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
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Markus Neteler]

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
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Vaclav Petras]

On Mon, May 31, 2021 at 4:10 PM Markus Neteler  wrote:

>
> ... unless we modify g.extension for now to continue to read from
> "grass-addons/grass7/"...
>
> Opinions?
>

+1 for "grass-addons/grass7/". Confusing for those who see the URL, but
good enough for now.

I started the transition for addons, but there are things to be decided.
See:

https://github.com/OSGeo/grass-addons/pull/535
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Markus Neteler]

On Mon, May 31, 2021 at 9:13 PM Markus Neteler  wrote:
>
> Hi devs,
>
> First step done:
> GRASS GIS 8.0 changes in master
> (https://github.com/OSGeo/grass/pull/1597) are merged!

One problem to address soon is the absence of "grass8" in the Addons
repo, leading to errors in the CI and all related docker builds:

(log example)
 Fetching  from GRASS GIS Addons repository (be patient)...
  E17: URL 
'https://github.com/OSGeo/grass-addons/trunk/grass8/raster/r.in.pdal'
doesn't exist

This requires to decide on

Restructure repository for version 8
https://github.com/OSGeo/grass-addons/issues/528

... unless we modify g.extension for now to continue to read from
"grass-addons/grass7/"...

Opinions?

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Markus Neteler]

Hi devs,

First step done:
GRASS GIS 8.0 changes in master
(https://github.com/OSGeo/grass/pull/1597) are merged!

Next step: test compilation and soonish create a "throw-away"
8.0.0alpha branch for testing.

cheers,
Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Michael Barton]

+1 for me
_
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Director, Network for Computational Modeling in Social & Ecological Sciences
Associate Director, School of Complex Adaptive Systems
Professor, School of Human Evolution & Social Change
Arizona State University
Tempe, AZ  85287-2402
USA

voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671(SHESC), 480-727-0709 (CSDC)
www: http://shesc.asu.edu, https://complexity.asu.edu, 
http://www.public.asu.edu/~cmbarton

On May 29, 2021, at 12:00 PM, 
grass-dev-requ...@lists.osgeo.org<mailto:grass-dev-requ...@lists.osgeo.org> 
wrote:

Date: Sat, 29 May 2021 10:58:59 +0200
From: Markus Neteler mailto:nete...@osgeo.org>>
To: GRASS developers list 
mailto:grass-dev@lists.osgeo.org>>
Subject: Re: [GRASS-dev] [release planning] GRASS GIS 8: create new
release branch
Message-ID:
mailto:CALFmHhtKU_X7UwQ5iqi+gNpqLY2cP1cBVcBvYqw9yQ8Y=fe...@mail.gmail.com>>
Content-Type: text/plain; charset="UTF-8"

Hi devs,

After a lot of editing and discussions in the following PR I meanwhile
also believe that it is becoming the preparation of the master branch
for G8:

"GRASS GIS 8.0 changes"
https://urldefense.com/v3/__https://github.com/OSGeo/grass/pull/1597__;!!IKRxdwAv5BmarQ!IgK2pDznYwXOP8vYETthOJrMnhhD4ZtuU30GyCTCcJVwPMbqjePMD96spCPSdKl5m8Q$

That means:
- merge this PR into the master branch (it is not perfect, but let's
move on and create separate PR(s) for the Windows related issues)
- branch off a "8.0.0alpha" branch, just as a "throw away/ignore later" branch
- create at a later stage the official "release_branch_8_0" after
having gained some experience with the "throw away" 8.0.0alpha branch.

If there are no objections I'd merge PR 1597 in the next days.
Note: the changes include (except for Windows) the simplification of
the startup script name (grass79/grass80 --> grass).

Markus

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Veronica Andreo]

+1 from my side too

Time to move forward!

El sáb., 29 may. 2021 08:37, Moritz Lennert 
escribió:

>
>
> Le 29 mai 2021 08:58:59 GMT+00:00, Markus Neteler  a
> écrit :
>
> >If there are no objections I'd merge PR 1597 in the next days.
>
> +1
>
> I think at this stage it should just happen, especially if it's a
> throw-away branch.
>
> Moritz
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Moritz Lennert]

Le 29 mai 2021 08:58:59 GMT+00:00, Markus Neteler  a écrit :

>If there are no objections I'd merge PR 1597 in the next days.

+1

I think at this stage it should just happen, especially if it's a throw-away 
branch.

Moritz
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Markus Neteler]

Hi devs,

After a lot of editing and discussions in the following PR I meanwhile
also believe that it is becoming the preparation of the master branch
for G8:

"GRASS GIS 8.0 changes"
https://github.com/OSGeo/grass/pull/1597

That means:
- merge this PR into the master branch (it is not perfect, but let's
move on and create separate PR(s) for the Windows related issues)
- branch off a "8.0.0alpha" branch, just as a "throw away/ignore later" branch
- create at a later stage the official "release_branch_8_0" after
having gained some experience with the "throw away" 8.0.0alpha branch.

If there are no objections I'd merge PR 1597 in the next days.
Note: the changes include (except for Windows) the simplification of
the startup script name (grass79/grass80 --> grass).

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Markus Neteler]

On Fri, May 21, 2021 at 4:02 PM Veronica Andreo  wrote:
> El jue, 20 may 2021 a las 17:21, Maris Nartiss () 
> escribió:
>> 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 – 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.

+1

> 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

(the time shrinked to days, meanwhile...)

> needed to complete ongoing development at least up to a working version that 
> can be merged.
>
> @Maris Nartiss what do you think?

For easier testing, I have prepared a GRASS GIS 8.0.0alpha PR:
https://github.com/OSGeo/grass/pull/1597

Do not merge, but try it out locally.

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Veronica Andreo]

Hi all,

El jue, 20 may 2021 a las 17:21, Maris Nartiss ()
escribió:

> Hello Makrus et al.
>
> 2021-05-15 16:40 GMT+03:00, Markus Neteler :
> > On Sat, May 15, 2021 at 4:05 AM Vaclav Petras 
> wrote:
> >> On Fri, May 14, 2021 at 11:10 AM Markus Neteler 
> >> 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 – 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  what do you think?

my 0.2 cents
Vero
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Maris Nartiss]

Hello Makrus et al.

2021-05-15 16:40 GMT+03:00, Markus Neteler :
> On Sat, May 15, 2021 at 4:05 AM Vaclav Petras  wrote:
>> On Fri, May 14, 2021 at 11:10 AM Markus Neteler 
>> 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 – management
module can be then created as a separate PR at some point later.

I would go with branching 8 off just before release. Do we have some
large PRs coming in for 8.1 that can not wait?

> Markus

Māris.

https://github.com/OSGeo/grass/pull/1501
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Michael Barton]

I guess I already filed an issue awhile back #851.

Michael
_
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Director, Network for Computational Modeling in Social & Ecological Sciences
Associate Director, School of Complex Adaptive Systems
Professor, School of Human Evolution & Social Change
Arizona State University
Tempe, AZ  85287-2402
USA

voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671(SHESC), 480-727-0709 (CSDC)
www: http://shesc.asu.edu, https://complexity.asu.edu, 
http://www.public.asu.edu/~cmbarton

On May 16, 2021, at 1:32 PM, 
grass-dev-requ...@lists.osgeo.org<mailto:grass-dev-requ...@lists.osgeo.org> 
wrote:

Date: Sun, 16 May 2021 20:32:05 +
From: Michael Barton mailto:michael.bar...@asu.edu>>
To: Vaclav Petras mailto:wenzesl...@gmail.com>>
Cc: GRASS developers 
mailto:grass-dev@lists.osgeo.org>>
Subject: Re: [GRASS-dev] [release planning] GRASS GIS 8: create new
release branch
Message-ID: 
<4efd251e-3f40-477e-a9ab-fa2a8b74e...@asu.edu<mailto:4efd251e-3f40-477e-a9ab-fa2a8b74e...@asu.edu>>
Content-Type: text/plain; charset="us-ascii"

v.in.pdal is not an extension though. It is packaged with the normal 
distribution. I guess I'll put in an issue to have it on the menu.

Michael

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Michael Barton]

v.in.pdal is not an extension though. It is packaged with the normal 
distribution. I guess I'll put in an issue to have it on the menu.

Michael
_
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Director, Network for Computational Modeling in Social & Ecological Sciences
Associate Director, School of Complex Adaptive Systems
Professor, School of Human Evolution & Social Change
Arizona State University
Tempe, AZ  85287-2402
USA

voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671(SHESC), 480-727-0709 (CSDC)
www: http://shesc.asu.edu, https://complexity.asu.edu, 
http://www.public.asu.edu/~cmbarton

On May 14, 2021, at 7:18 PM, Vaclav Petras 
mailto:wenzesl...@gmail.com>> wrote:


On Fri, May 14, 2021 at 3:54 PM Michael Barton 
mailto:michael.bar...@asu.edu>> wrote:
The r.colors/v.colors log scaling was getting close to being fixed. But I don't 
know if Huidae has had time to work on it recently.

Related to vector colors with v.colors, I also wanted to change how d.vect 
works with colors of areas, but I'm unsure about how to proceed there.

https://github.com/OSGeo/grass/pull/1146

It would be very nice to have increasing PDAL functionality by adding r.in.pdal.

More work is needed, so probably not for the initial beta, but we are in a good 
position to include it as is if we find ourselves before the release without 
r.in.pdal.

Along those lines, why doesn't v.in.pdal show up in the menu? I thought that 
was supposed to be automatic now.

The menus are handcrafted - there is a strutructure which is in the menus 
(i.e., nothing in the modules themselves is used to sort them out 
hierarchically). What is automatic is the Addons: If you install the 
script-based r.in.pdal from Addons, it will show up automatically.

https://grass.osgeo.org/grass78/manuals/addons/r.in.pdal.html


Michael
_
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Director, Network for Computational Modeling in Social & Ecological Sciences
Associate Director, School of Complex Adaptive Systems
Professor, School of Human Evolution & Social Change
Arizona State University
Tempe, AZ  85287-2402
USA

voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671(SHESC), 480-727-0709 (CSDC)
www: http://shesc.asu.edu, 
https://complexity.asu.edu, 
http://www.public.asu.edu/~cmbarton

On May 14, 2021, at 12:00 PM, 
grass-dev-requ...@lists.osgeo.org 
wrote:

Date: Fri, 14 May 2021 17:09:42 +0200
From: Markus Neteler mailto:nete...@osgeo.org>>
To: GRASS developers list 
mailto:grass-dev@lists.osgeo.org>>
Subject: [GRASS-dev] [release planning] GRASS GIS 8: create new
release branch
Message-ID:
mailto:calfmhhsn3iobnqeplk6xjwcdwljmmvvjf9sdhyt_zzjyn_f...@mail.gmail.com>>
Content-Type: text/plain; charset="UTF-8"

Hi devs,

Let me suggest to create a new release branch in the next two weeks
It will help us to focus on the upcoming and even announced 8.0.0
release: several conferences are upcoming with presentations on GRASS
GIS 8 talks and demo sessions.
So it makes quite sense to have a tangible version available, at least
in a release branch :-)

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?

See e.g. here:
https://urldefense.com/v3/__https://github.com/OSGeo/grass/milestone/4__;!!IKRxdwAv5BmarQ!JtOeB64Z2SqQTOloVuAXNvAXbCfC0qKPQxI4A_vowo7SrHYm57hU_Z4GAxC1VRBwidOIuio$

See also (please add notes!):
Draft release notes: 
https://urldefense.com/v3/__https://trac.osgeo.org/grass/wiki/Grass8/NewFeatures80__;!!IKRxdwAv5BmarQ!JtOeB64Z2SqQTOloVuAXNvAXbCfC0qKPQxI4A_vowo7SrHYm57hU_Z4GAxC1VRBwKx_wSAs$

Thanks,
Markus

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Markus Neteler]

On Sat, May 15, 2021 at 4:05 AM Vaclav Petras  wrote:
> On Fri, May 14, 2021 at 11:10 AM Markus Neteler  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?

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Markus Neteler]

Denis,

On Fri, May 14, 2021 at 10:12 PM Denis Ovsienko  wrote:
>
> On Fri, 14 May 2021 17:09:42 +0200
> Markus Neteler  wrote:
>
> [...]
> > 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?

#1237: parser: fixup more messages
--> looks good, will you merge it?

#1421 r.geomorphon: fix landform category names
--> I have added a comment, related to the HTML page content

#1569 (fixes #1420) r.in.poly: do not try to use stdin as input
#1570 (fixes #1355) r.geomorphon: remove multires-specific code
--> will you merge them?

> These are all trivial bugfixes.
> --
> Denis Ovsienko

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Vaclav Petras]

On Fri, May 14, 2021 at 3:54 PM Michael Barton 
wrote:

> The r.colors/v.colors log scaling was getting close to being fixed. But I
> don't know if Huidae has had time to work on it recently.
>

Related to vector colors with v.colors, I also wanted to change how d.vect
works with colors of areas, but I'm unsure about how to proceed there.

https://github.com/OSGeo/grass/pull/1146


> It would be very nice to have increasing PDAL functionality by adding
> r.in.pdal.
>

More work is needed, so probably not for the initial beta, but we are in a
good position to include it as is if we find ourselves before the release
without r.in.pdal.


> Along those lines, why doesn't v.in.pdal show up in the menu? I thought
> that was supposed to be automatic now.
>

The menus are handcrafted - there is a strutructure which is in the menus
(i.e., nothing in the modules themselves is used to sort them out
hierarchically). What is automatic is the Addons: If you install the
script-based r.in.pdal from Addons, it will show up automatically.

https://grass.osgeo.org/grass78/manuals/addons/r.in.pdal.html


>
> Michael
> _
> C. Michael Barton
> Director, Center for Social Dynamics & Complexity
> Director, Network for Computational Modeling in Social & Ecological
> Sciences
> Associate Director, School of Complex Adaptive Systems
> Professor, School of Human Evolution & Social Change
> Arizona State University
> Tempe, AZ  85287-2402
> USA
>
> voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
> fax: 480-965-7671(SHESC), 480-727-0709 (CSDC)
> www: http://shesc.asu.edu, https://complexity.asu.edu,
> http://www.public.asu.edu/~cmbarton
>
> On May 14, 2021, at 12:00 PM, grass-dev-requ...@lists.osgeo.org wrote:
>
> Date: Fri, 14 May 2021 17:09:42 +0200
> From: Markus Neteler 
> To: GRASS developers list 
> Subject: [GRASS-dev] [release planning] GRASS GIS 8: create new
> release branch
> Message-ID:
> 
> Content-Type: text/plain; charset="UTF-8"
>
> Hi devs,
>
> Let me suggest to create a new release branch in the next two weeks
> It will help us to focus on the upcoming and even announced 8.0.0
> release: several conferences are upcoming with presentations on GRASS
> GIS 8 talks and demo sessions.
> So it makes quite sense to have a tangible version available, at least
> in a release branch :-)
>
> 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?
>
> See e.g. here:
>
> https://urldefense.com/v3/__https://github.com/OSGeo/grass/milestone/4__;!!IKRxdwAv5BmarQ!JtOeB64Z2SqQTOloVuAXNvAXbCfC0qKPQxI4A_vowo7SrHYm57hU_Z4GAxC1VRBwidOIuio$
>
>
> See also (please add notes!):
> Draft release notes:
> https://urldefense.com/v3/__https://trac.osgeo.org/grass/wiki/Grass8/NewFeatures80__;!!IKRxdwAv5BmarQ!JtOeB64Z2SqQTOloVuAXNvAXbCfC0qKPQxI4A_vowo7SrHYm57hU_Z4GAxC1VRBwKx_wSAs$
>
>
> Thanks,
> Markus
>
>
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Vaclav Petras]

On Fri, May 14, 2021 at 11:10 AM Markus Neteler  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, 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.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Denis Ovsienko]

On Fri, 14 May 2021 17:09:42 +0200
Markus Neteler  wrote:

[...]
> 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?

#1237
#1421
#1569 (fixes #1420)
#1570 (fixes #1355)

These are all trivial bugfixes.

-- 
Denis Ovsienko
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Michael Barton]

The r.colors/v.colors log scaling was getting close to being fixed. But I don't 
know if Huidae has had time to work on it recently.

It would be very nice to have increasing PDAL functionality by adding 
r.in.pdal. Along those lines, why doesn't v.in.pdal show up in the menu? I 
thought that was supposed to be automatic now. It is present in both 7.8 and 
7.9 if configures --with-pdal.

Michael
_
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Director, Network for Computational Modeling in Social & Ecological Sciences
Associate Director, School of Complex Adaptive Systems
Professor, School of Human Evolution & Social Change
Arizona State University
Tempe, AZ  85287-2402
USA

voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671(SHESC), 480-727-0709 (CSDC)
www: http://shesc.asu.edu, https://complexity.asu.edu, 
http://www.public.asu.edu/~cmbarton

On May 14, 2021, at 12:00 PM, 
grass-dev-requ...@lists.osgeo.org 
wrote:

Date: Fri, 14 May 2021 17:09:42 +0200
From: Markus Neteler mailto:nete...@osgeo.org>>
To: GRASS developers list 
mailto:grass-dev@lists.osgeo.org>>
Subject: [GRASS-dev] [release planning] GRASS GIS 8: create new
release branch
Message-ID:
mailto:calfmhhsn3iobnqeplk6xjwcdwljmmvvjf9sdhyt_zzjyn_f...@mail.gmail.com>>
Content-Type: text/plain; charset="UTF-8"

Hi devs,

Let me suggest to create a new release branch in the next two weeks
It will help us to focus on the upcoming and even announced 8.0.0
release: several conferences are upcoming with presentations on GRASS
GIS 8 talks and demo sessions.
So it makes quite sense to have a tangible version available, at least
in a release branch :-)

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?

See e.g. here:
https://urldefense.com/v3/__https://github.com/OSGeo/grass/milestone/4__;!!IKRxdwAv5BmarQ!JtOeB64Z2SqQTOloVuAXNvAXbCfC0qKPQxI4A_vowo7SrHYm57hU_Z4GAxC1VRBwidOIuio$

See also (please add notes!):
Draft release notes: 
https://urldefense.com/v3/__https://trac.osgeo.org/grass/wiki/Grass8/NewFeatures80__;!!IKRxdwAv5BmarQ!JtOeB64Z2SqQTOloVuAXNvAXbCfC0qKPQxI4A_vowo7SrHYm57hU_Z4GAxC1VRBwKx_wSAs$

Thanks,
Markus

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev