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
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
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
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
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
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.
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
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
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
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
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.
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
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
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
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
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
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
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
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
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
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
ass-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: cre
+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,
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
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,
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
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
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
S 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&q
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
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
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
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,
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
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
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
36 matches
Mail list logo
