Hi devs,
we need to decide about the next milestone: do we want
- 7.8.5, or
- 7.10 , or
- 8.0.0
Markus
Markus Neteler wrote
Hi devs,
we need to decide about the next milestone: do we want
- 7.8.5, or
- 7.10 , or
- 8.0.0
I remember there was a discussion about that; though what was the outcome
then?
what would be justifying 8.0.0? e.g.
- new startup wizzard
- updated PROJ > 6 support
- improved data catalog
- anything else?
-----
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
Hello Markus,
we are planning in few days a survey (probably a Google Form) that will gather opinions about some things regarding New startup (e.g. question of workspaces (starting GRASS from icon), how start If a last mapset is not usable, or a question of first-time user mode).
According to this survey that is meant especially for experienced users we will set up further dev in terms of these things. So we are not finished here yet.
Now I am working on the theoretical background for my diploma thesis but I am planning to involve in practical part soon.
Hopefully, the survey would be a good way how to set up next steps. 
Linda
10. 10. 2020 v 18:24, Markus Neteler <neteler@osgeo.org>:
Hi devs,
we need to decide about the next milestone: do we want
- 7.8.5, or
- 7.10 , or
- 8.0.0Markus
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
On Sat, Oct 10, 2020 at 8:19 PM Helmut Kudrnovsky <hellik@web.de> wrote:
Markus Neteler wrote
Hi devs,
we need to decide about the next milestone: do we want
- 7.8.5, or
- 7.10 , or
- 8.0.0
I remember there was a discussion about that; though what was the outcome
then?what would be justifying 8.0.0? e.g.
- new startup wizzard
- updated PROJ > 6 support
- improved data catalog
- anything else?
I am not a developer, but I would say the changes above are big enough to justify a jump to 7.10. For a next major version (v8.0), would that not be a good moment to introduce any changes that break things? Are there any?
best regards
HelmutSent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
Hi
El sáb., 10 oct. 2020 15:19, Helmut Kudrnovsky <hellik@web.de> escribió:
Markus Neteler wrote
Hi devs,
we need to decide about the next milestone: do we want
- 7.8.5, or
- 7.10 , or
- 8.0.0
I remember there was a discussion about that; though what was the outcome
then?what would be justifying 8.0.0? e.g.
- new startup wizzard
- updated PROJ > 6 support
- improved data catalog
- anything else?
image collections, it requires to update the temporal database. 7.8.x line does not read older tgrass db
My 0.2 cents
Vero
Hi Linda,
Looking forward to seeing your survey!
Best,
Tom
···
Thomas E Adams, III
1724 Sage Lane
Blacksburg, VA 24060
tea3rd@gmail.com (personal)
tea@terrapredictions.org (work)
1 (513) 739-9512 (cell)
Hi,
so 10. 10. 2020 v 18:21 odesílatel Markus Neteler <neteler@osgeo.org> napsal:
let's split obvious milestone from to-be-decided milestone.
we need to decide about the next milestone: do we want
- 7.8.5, or
refers to releasebranch_7_8 branch. GRASS 7.8.4 has been released
recently. There will be very probably another point version release in
three months (January 2021).
- 7.10 , or
- 8.0.0
Yes, it was discussed some time ago. I remember that we were inclined
to 8.0 [1] (scenario 3). Major reasons:
* image collections (breaks TGIS backward compatibility)
* new startup (GSoC)
I think it could be realistic to release 8.0.0 in the first quarter of
2021 (Feb?).
Martin
[1] https://trac.osgeo.org/grass/wiki/Release/Schedule#Scenario3
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
Hi,
just to confirm what Martin and Vero were saying, the problem is we have breaking changes (TGIS) in master and new, fairly major features (data catalog, new startup mechanism) and probably some other things, so we can’t simply branch off 7.10 without disabling those. So that’s why during the recent call we had we leaned towards releasing 8. I agree beginning of 2021 should be realistic, although I am not sure what is the timeline of the PROJ changes.
We have the GRASS 8 ideas here, so it would be worth reviewing what could be realistically accomplished:
https://trac.osgeo.org/grass/wiki/Grass8Planning
Anna
On Sun, Oct 11, 2020 at 1:15 PM Martin Landa <landa.martin@gmail.com> wrote:
Hi,
so 10. 10. 2020 v 18:21 odesílatel Markus Neteler <neteler@osgeo.org> napsal:
let’s split obvious milestone from to-be-decided milestone.
we need to decide about the next milestone: do we want
- 7.8.5, or
refers to releasebranch_7_8 branch. GRASS 7.8.4 has been released
recently. There will be very probably another point version release in
three months (January 2021).
- 7.10 , or
- 8.0.0
Yes, it was discussed some time ago. I remember that we were inclined
to 8.0 [1] (scenario 3). Major reasons:
- image collections (breaks TGIS backward compatibility)
- new startup (GSoC)
I think it could be realistic to release 8.0.0 in the first quarter of
2021 (Feb?).Martin
[1] https://trac.osgeo.org/grass/wiki/Release/Schedule#Scenario3
–
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
On 11/10/20 19:15, Martin Landa wrote:
Hi,
so 10. 10. 2020 v 18:21 odesílatel Markus Neteler <neteler@osgeo.org> napsal:
let's split obvious milestone from to-be-decided milestone.
we need to decide about the next milestone: do we want
- 7.8.5, or
refers to releasebranch_7_8 branch. GRASS 7.8.4 has been released
recently. There will be very probably another point version release in
three months (January 2021).- 7.10 , or
- 8.0.0Yes, it was discussed some time ago. I remember that we were inclined
to 8.0 [1] (scenario 3). Major reasons:* image collections (breaks TGIS backward compatibility)
* new startup (GSoC)
+1
Moritz
On 2020-10-13 10:29 a.m., Anna Petrášová wrote:
Hi,
just to confirm what Martin and Vero were saying, the problem is we have breaking changes (TGIS) in master and new, fairly major features (data catalog, new startup mechanism) and probably some other things, so we can't simply branch off 7.10 without disabling those. So that's why during the recent call we had we leaned towards releasing 8. I agree beginning of 2021 should be realistic, although I am not sure what is the timeline of the PROJ changes.
We have the GRASS 8 ideas here, so it would be worth reviewing what could be realistically accomplished:
https://trac.osgeo.org/grass/wiki/Grass8PlanningAnna
Regarding PROJ, some critical changes are coming for the PROJ 7.2.0 release on 1st November (a lot has to do with network/SSL/CA bundle, which is important these days), and then another release 7.2.1 is set for 1st January, which could work nicely with your planned early 2021 timeline for GRASS. (PROJ always stays strict to those planned release dates)
-jeff
--
Jeff McKenna
MapServer Consulting and Training Services
co-founder of FOSS4G
http://gatewaygeo.com/
On 2020-10-13 10:42 a.m., Jeff McKenna wrote:
On 2020-10-13 10:29 a.m., Anna Petrášová wrote:
Hi,
just to confirm what Martin and Vero were saying, the problem is we have breaking changes (TGIS) in master and new, fairly major features (data catalog, new startup mechanism) and probably some other things, so we can't simply branch off 7.10 without disabling those. So that's why during the recent call we had we leaned towards releasing 8. I agree beginning of 2021 should be realistic, although I am not sure what is the timeline of the PROJ changes.
We have the GRASS 8 ideas here, so it would be worth reviewing what could be realistically accomplished:
https://trac.osgeo.org/grass/wiki/Grass8PlanningAnna
Regarding PROJ, some critical changes are coming for the PROJ 7.2.0 release on 1st November (a lot has to do with network/SSL/CA bundle, which is important these days), and then another release 7.2.1 is set for 1st January, which could work nicely with your planned early 2021 timeline for GRASS. (PROJ always stays strict to those planned release dates)
-jeff
I should also mention that PROJ 7.2.0 will also importantly be the first release with the new EPSG database model (v10), which GRASS and so many other software depend on (EPSG geodetic database for projection lookup). That could also be an important upcoming change for GRASS to leverage.
-jeff
--
Jeff McKenna
MapServer Consulting and Training Services
co-founder of FOSS4G
http://gatewaygeo.com/
Regarding PROJ, some critical changes are coming for the PROJ 7.2.0
release on 1st November (a lot has to do with network/SSL/CA bundle,
which is important these days), and then another release 7.2.1 is set
for 1st January, which could work nicely with your planned early 2021
timeline for GRASS. (PROJ always stays strict to those planned release
dates)
-jeff
I should also mention that PROJ 7.2.0 will also importantly be the first
release with the new EPSG database model (v10), which GRASS and so many
other software depend on (EPSG geodetic database for projection lookup).
That could also be an important upcoming change for GRASS to leverage.
I should moderate this in saying that despite PROJ 7.2.0 undergoing internally significant changes w.r.t its database, they are done in such a way that they are intended to be mostly internal details with none or little outside visibility. See https://github.com/OSGeo/PROJ/pull/2370 for details of the changes. So hopefully this release will not be significantly different than another one where the EPSG database is updated, where content can change a bit.
PROJ 8.0 will expose a new concept, DatumEnsemble, which might impact some downstream users that currently use proj_crs_get_datum(), but GRASS doesn’t seem to use according to
https://github.com/OSGeo/grass/search?q=proj_crs_get_datum , so there’s good chance that the impact will be minimal too. See
https://github.com/OSGeo/PROJ/pull/2371 for details
So don’t panick 
Even
–
Spatialys - Geospatial professional services