Re: [GRASS-PSC] [GRASS-dev] planning releases - spring 2018

2018-02-27 Thread Markus Neteler 
On Tue, Feb 27, 2018 at 10:14 PM, Martin Landa  wrote:
> Hi,
>
> major release 7.4.0 is almost one month old, we should think about
> time schedule for a next releases. Assuming that we are trying to
> release new (point) version every three/four months, 7.4.1 could be
> schedule to May [1].

That's good. Perhaps even earlier? Because I would like to see a new
release with ZSTD compression included since I cannot run trunk in
production and hesitate to heavily patch 7.4. locally. That would be
7.6.0 then.

Yet some backports are open for 7.4.1 [4]

> Meanwhile we could also release 7.2.3 [2] (7.2.2 has been released in
> 16/9/2017). In March or later (see overall of changes [3]), what do
> you think?

Yes, a new 7.2.3 release soon as well. Yesterday I submitted a fix it
since it failed to compile on Fedora 28. Some other distros should be
tested as well before releasing (however, that does not take ages).
Maybe that would become the last 7.2.x then? We'll see.

Also some backports are desired here: [5]

While we are at it, I would also package up without big marketing hype
a new 7.0.6 release [6], just to make it an official tarball. It
contains some updates you don't want to miss if still using 7.0 for
whatever reason.

Markus

> [1] https://trac.osgeo.org/grass/milestone/7.4.1
> [2] https://trac.osgeo.org/grass/milestone/7.2.3
> [3] 
> https://trac.osgeo.org/grass/changeset?reponame=&new=72284%40grass%2Fbranches%2Freleasebranch_7_2&old=71497%40grass%2Fbranches%2Freleasebranch_7_2

[4] https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.4.1tobebackported
[5] https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.2.3tobebackported
[6] https://trac.osgeo.org/grass/milestone/7.0.6
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [GRASS-dev] planning releases - spring 2018

2018-03-02 Thread Martin Landa 
Hi,

2018-02-27 23:30 GMT+01:00 Markus Neteler :
> Yet some backports are open for 7.4.1 [4]
> [4] https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.4.1tobebackporte

preferable authors should do backports because they can decide best
(mmetz, wenzeslaus, marisn)

Ma

-- 
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [GRASS-dev] planning releases - spring 2018

2018-03-02 Thread Michael Barton 
I hope that the non-functional digitizer and semi-functional pull-down control 
can be fixed for Mac.

Michael

C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University

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















On Feb 27, 2018, at 3:30 PM, Markus Neteler 
mailto:nete...@osgeo.org>> wrote:

On Tue, Feb 27, 2018 at 10:14 PM, Martin Landa 
mailto:landa.mar...@gmail.com>> wrote:
Hi,

major release 7.4.0 is almost one month old, we should think about
time schedule for a next releases. Assuming that we are trying to
release new (point) version every three/four months, 7.4.1 could be
schedule to May [1].

That's good. Perhaps even earlier? Because I would like to see a new
release with ZSTD compression included since I cannot run trunk in
production and hesitate to heavily patch 7.4. locally. That would be
7.6.0 then.

Yet some backports are open for 7.4.1 [4]

Meanwhile we could also release 7.2.3 [2] (7.2.2 has been released in
16/9/2017). In March or later (see overall of changes [3]), what do
you think?

Yes, a new 7.2.3 release soon as well. Yesterday I submitted a fix it
since it failed to compile on Fedora 28. Some other distros should be
tested as well before releasing (however, that does not take ages).
Maybe that would become the last 7.2.x then? We'll see.

Also some backports are desired here: [5]

While we are at it, I would also package up without big marketing hype
a new 7.0.6 release [6], just to make it an official tarball. It
contains some updates you don't want to miss if still using 7.0 for
whatever reason.

Markus

[1] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__trac.osgeo.org_grass_milestone_7.4.1&d=DwIGaQ&c=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ&r=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0&m=xQ__h-TZ2aXaou26BV6e8rnUJAxAmpIdbPv6CyQoxZQ&s=yAC3qoDi2aRkLTakTAOWoCW04wi9b-UMn8XCyao4mPA&e=
[2] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__trac.osgeo.org_grass_milestone_7.2.3&d=DwIGaQ&c=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ&r=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0&m=xQ__h-TZ2aXaou26BV6e8rnUJAxAmpIdbPv6CyQoxZQ&s=ALpFL4wguP217QJ81M7V12qpOFULdWpJcpSq_nxX95s&e=
[3] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__trac.osgeo.org_grass_changeset-3Freponame-3D-26new-3D72284-2540grass-252Fbranches-252Freleasebranch-5F7-5F2-26old-3D71497-2540grass-252Fbranches-252Freleasebranch-5F7-5F2&d=DwIGaQ&c=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ&r=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0&m=xQ__h-TZ2aXaou26BV6e8rnUJAxAmpIdbPv6CyQoxZQ&s=LpdQSyCNh1RxeOb6XFKVqKOWaklQ6-ndhAob3gCUpOM&e=

[4] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__trac.osgeo.org_grass_wiki_Grass7Planning-23a7.4.1tobebackported&d=DwIGaQ&c=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ&r=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0&m=xQ__h-TZ2aXaou26BV6e8rnUJAxAmpIdbPv6CyQoxZQ&s=9CUm1iT0HSaGEqdQD2lFxgO8sffPscN3UvzOQjPaHc0&e=
[5] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__trac.osgeo.org_grass_wiki_Grass7Planning-23a7.2.3tobebackported&d=DwIGaQ&c=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ&r=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0&m=xQ__h-TZ2aXaou26BV6e8rnUJAxAmpIdbPv6CyQoxZQ&s=WUkMKjORTS3ciUC1VwNeauZuFK_n9x27SBNxsbcwYtw&e=
[6] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__trac.osgeo.org_grass_milestone_7.0.6&d=DwIGaQ&c=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ&r=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0&m=xQ__h-TZ2aXaou26BV6e8rnUJAxAmpIdbPv6CyQoxZQ&s=zjnek9NRFrIY9FiCiUvNQg8Dj9kdT6mdVXuj4oTH4oE&e=
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.osgeo.org_mailman_listinfo_grass-2Dpsc&d=DwIGaQ&c=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ&r=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0&m=xQ__h-TZ2aXaou26BV6e8rnUJAxAmpIdbPv6CyQoxZQ&s=mCdqd-llBum8Nte19J3ouwbCzWHhgOZ4Vn-wyykM6CE&e=

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

Re: [GRASS-PSC] [GRASS-dev] planning releases - spring 2018

2018-03-04 Thread Markus Neteler 
On Tue, Feb 27, 2018 at 11:30 PM, Markus Neteler  wrote:
> On Tue, Feb 27, 2018 at 10:14 PM, Martin Landa  wrote:
>> Hi,
>>
>> major release 7.4.0 is almost one month old, we should think about
>> time schedule for a next releases. Assuming that we are trying to
>> release new (point) version every three/four months, 7.4.1 could be
>> schedule to May [1].
>
> That's good. Perhaps even earlier? Because I would like to see a new
> release with ZSTD compression included since I cannot run trunk in
> production and hesitate to heavily patch 7.4. locally. That would be
> 7.6.0 then.

Indeed we may create a new 7.6 branch already earlier and phase out 7.2.

> Yet some backports are open for 7.4.1 [4]
>
>> Meanwhile we could also release 7.2.3 [2] (7.2.2 has been released in
>> 16/9/2017). In March or later (see overall of changes [3]), what do
>> you think?
>
> Yes, a new 7.2.3 release soon as well. Yesterday I submitted a fix it
> since it failed to compile on Fedora 28. Some other distros should be
> tested as well before releasing (however, that does not take ages).
> Maybe that would become the last 7.2.x then? We'll see.
>
> Also some backports are desired here: [5]

For 7.2.3, I see only these relevant candidates left:

* i18N: Install gettext to Python script modules to use translated
strings extracted by r70817: r70818
* r.grow.distance: clean up after r68611: r69327

As Martin wrote: the authors in trunk may judge (here: Maris and
Vaclav, respectively).

I have started a draft trac page (please update as needed):
https://trac.osgeo.org/grass/wiki/Release/7.2.3-News

Markus


>> [1] https://trac.osgeo.org/grass/milestone/7.4.1
>> [2] https://trac.osgeo.org/grass/milestone/7.2.3
>> [3] 
>> https://trac.osgeo.org/grass/changeset?reponame=&new=72284%40grass%2Fbranches%2Freleasebranch_7_2&old=71497%40grass%2Fbranches%2Freleasebranch_7_2
>
> [4] https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.4.1tobebackported
> [5] https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.2.3tobebackported
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [GRASS-dev] planning releases - spring 2018

2018-03-04 Thread Vaclav Petras 
On Sun, Mar 4, 2018 at 1:59 PM, Markus Neteler  wrote:

> On Tue, Feb 27, 2018 at 11:30 PM, Markus Neteler 
> wrote:
>


> As Martin wrote: the authors in trunk may judge (here: Maris and
> Vaclav, respectively).
>

I did the one which was there and crossed it out already. Is there anything
else?

https://trac.osgeo.org/grass/changeset/72295
https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.4.1tobebackporte
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [GRASS-dev] planning releases - spring 2018

2018-03-05 Thread Markus Neteler 
Hi devs,

just FYI - the roadmap is now updated according to latest discussions here:

https://trac.osgeo.org/grass/roadmap

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

Re: [GRASS-PSC] [GRASS-dev] planning releases - spring 2018

2018-03-09 Thread Martin Landa 
Hi,

2018-03-05 23:15 GMT+01:00 Markus Neteler :

I created a draft for 7.4.1 and added recently backported new features
of Graphical Modeler [1]. Please free to update the draft by adding
cool features implemented by you :-) Ma

[1] 
https://trac.osgeo.org/grass/wiki/Release/7.4.1-News#ImprovementsintheGraphicalUserInterface

-- 
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc

Re: [GRASS-PSC] [GRASS-dev] planning releases - spring 2018

2018-03-25 Thread Moritz Lennert 


Am 25. März 2018 12:32:24 MESZ schrieb Martin Landa :
>Dear all,
>
>2018-02-27 22:14 GMT+01:00 Martin Landa :
>> major release 7.4.0 is almost one month old, we should think about
>> time schedule for a next releases. Assuming that we are trying to
>> release new (point) version every three/four months, 7.4.1 could be
>> schedule to May [1].
>> [1] https://trac.osgeo.org/grass/milestone/7.4.1
>
>I would propose based on planned time schedule soft freeze starting by
>tomorrow (Mon 26/3).


+1

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