2017-08-14 12:04 GMT+02:00 Martin Landa <landa.martin@gmail.com>:
2017-08-14 11:54 GMT+02:00 Martin Landa <landa.martin@gmail.com>:
C:/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/bin/r.in.lidar.exe:
error while loading shared libraries: libgrass_raster.7.3.svn.dll:
cannot open shared object file: No such file or directory
it's seems to be magically fixed be reinstalling msvcrt2013 package.
Will wait for the next build. Ma
On Wed, Jun 28, 2017 at 11:02 PM, Markus Neteler <neteler@osgeo.org> wrote:
Hi all,
GRASS 7.2.1 has been released on 3rd May 2017, so time to plan the
next release, i.e. 7.2.2. Currently 7.2.2 release is planned in July
[1]. It would mean, following RFC4 [2] using [3]:
2017-07-05 - soft freeze (only bugfixes)
2017-08-04 - hard freeze + RC1
2017-08-14 - RC2
2017-08-29 - final
... RC1 is out for a while and dust has settled.
I suggest to get out RC2 asap in order to still be able to roughly
meet the final release deadline.
On Wed, Jun 28, 2017 at 11:02 PM, Markus Neteler <neteler@osgeo.org> wrote:
Hi all,
GRASS 7.2.1 has been released on 3rd May 2017, so time to plan the
next release, i.e. 7.2.2. Currently 7.2.2 release is planned in July
[1]. It would mean, following RFC4 [2] using [3]:
2017-07-05 - soft freeze (only bugfixes)
2017-08-04 - hard freeze + RC1
2017-08-14 - RC2
2017-08-29 - final
... RC1 is out for a while and dust has settled.
I suggest to get out RC2 asap in order to still be able to roughly
meet the final release deadline.
Any objections?
None from me, but I would love a solution to #3402 before we release final...
On Wed, Jun 28, 2017 at 11:02 PM, Markus Neteler <neteler@osgeo.org> wrote:
Hi all,
GRASS 7.2.1 has been released on 3rd May 2017, so time to plan the
next release, i.e. 7.2.2. Currently 7.2.2 release is planned in July
[1]. It would mean, following RFC4 [2] using [3]:
2017-07-05 - soft freeze (only bugfixes)
2017-08-04 - hard freeze + RC1
2017-08-14 - RC2
2017-08-29 - final
... RC1 is out for a while and dust has settled.
I suggest to get out RC2 asap in order to still be able to roughly
meet the final release deadline.
Any objections?
None from me, but I would love a solution to #3402 before we release final...
#3402 seems fixed (backport to release72 : r71440)
Pietro has also cleaned up the unnecessary imports of builtins in trunk r71438, but this still needs backporting. Maybe we can wait with RC2 until this is done ?
On Sat, Aug 26, 2017 at 3:55 PM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:
...
#3402 seems fixed (backport to release72 : r71440)
Pietro has also cleaned up the unnecessary imports of builtins in trunk
r71438, but this still needs backporting. Maybe we can wait with RC2 until
this is done ?
On Sat, Aug 26, 2017 at 8:36 PM, Markus Neteler <neteler@osgeo.org> wrote:
On Sat, Aug 26, 2017 at 3:55 PM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:
...
> #3402 seems fixed (backport to release72 : r71440)
>
> Pietro has also cleaned up the unnecessary imports of builtins in trunk
> r71438, but this still needs backporting. Maybe we can wait with RC2
until
> this is done ?
On Sat, Aug 26, 2017 at 8:36 PM, Markus Neteler <neteler@osgeo.org <mailto:neteler@osgeo.org>> wrote:
On Sat, Aug 26, 2017 at 3:55 PM, Moritz Lennert
<mlennert@club.worldonline.be <mailto:mlennert@club.worldonline.be>>
wrote:
...
> #3402 seems fixed (backport to release72 : r71440)
>
> Pietro has also cleaned up the unnecessary imports of builtins in trunk
> r71438, but this still needs backporting. Maybe we can wait with RC2 until
> this is done ?
P.S. To be sure, testing should be done on other platforms as well.
Just to make sure the fixes didn't break anything else. Any testing of
python script modules and the GUI already helps with that.