#2636: v.buffer, allow selection of columns for opts "distance",
"minordistance",
and "angle"
--+-
Reporter: isaacullah | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.
Hi,
on web page we claim:
New stable long term support (LTS) release: GRASS GIS 7.0.3
We could adopt similar concept as QGIS.
next LTS will be 7.0.4 (~April)
next stable release will be 7.2.0 (~Jule)
next LTS will be 7.2.1 (~October)
What do you think? Martin
--
Martin Landa
http://geo.fsv.c
#2480: v.class.ml: ImportError: No module named training_extraction
--+
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: Addons
#2480: v.class.ml: ImportError: No module named training_extraction
--+
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: Addons
#2968: g.extension problem with module containing various python files:
"ImportError: No module named"
-+-
Reporter: lrntct | Owner: martinl
Type: defect | Status: assigned
Priority: major | Milestone: 7.0.4
Component: Addo
#2480: v.class.ml: ImportError: No module named training_extraction
--+
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: Addons
#2947: g.gui.gmodeler - not possible to remove data from model
+--
Reporter: lfurtkevicova | Owner: martinl
Type: defect | Status: assigned
Priority: normal | Milestone: 7.0.4
Compone
#2854: results in winGRASS7 32bit vs 64bit: should they be identical?
-+-
Reporter: hellik | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.4
Component: Raster |Version: svn-rel
On Fri, Mar 25, 2016 at 2:14 AM, Pietro wrote:
>
> I commit some changes in pygrass (r68138), temporal library (r68139)
> and GRASS scripts (r68140) that were on my trunk from a bit...
Nice! But please, check the tests:
http://fatra.cnr.ncsu.edu/grassgistests/reports_for_date-2016-03-25-07-00
Hi,
firstly, thanks for your interest.
On Fri, Mar 25, 2016 at 3:12 AM, massimo di stefano wrote:"
can you please explain us your approach to develop a Qt based map canvas?
While the development of a window for each module is pretty straightforward
(the use of g.parser and a template.ui
#2225: Improvements python shell
--+---
Reporter: jradinger| Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.4
Component: wxGUI|Version: unspe
#2226: Get python command from copy-button
--+---
Reporter: jradinger| Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.1.0
Component: wxGUI|Version:
#2756: wxGUI CTRL+CAPS LOCK make the command line prompt font size smaller
-+-
Reporter: elena | Owner: grass-dev@…
Type: task| Status: closed
Priority: normal | Milestone: 7.0.4
Component: wxGUI |Version: 7.0.1
R
#2959: r.viewshed, r.terraflow and i.atcorr broken in 32/64bit builds
-+-
Reporter: wenzeslaus | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker | Milestone: 7.0.4
Component:
#2734: v.distance: 3d point inside area is classified as outside
---+-
Reporter: annakrat | Owner: grass-dev@…
Type: defect| Status: closed
Priority: normal| Milestone: 7.0.4
Component: Vector|Version: svn
#2734: v.distance: 3d point inside area is classified as outside
---+-
Reporter: annakrat | Owner: grass-dev@…
Type: defect| Status: new
Priority: normal| Milestone: 7.0.4
Component: Vector|Version: svn-tr
#2970: Replace Vect_point_in_box() by Vect_point_in_box_2d() where appropriate
-+-
Reporter: wenzeslaus | Owner: grass-dev@…
Type: task | Status: new
Priority: minor| Milestone: 7.1.0
Component:
#2959: r.viewshed, r.terraflow and i.atcorr broken in 32/64bit builds
-+-
Reporter: wenzeslaus | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker | Milestone: 7.0.4
Component:
#2845: Build failure with 7.0.3RC1 on Linux
-+-
Reporter: scimmia | Owner: grass-dev@…
Type: defect | Status: closed
Priority: blocker | Milestone: 7.0.4
Component: Compiling |Vers
#2871: lib/iostream/mm.cpp:Fails to build with GCC 6: declaration of ... has a
different exception specifier
+-
Reporter: sebastic | Owner: grass-dev@…
Type: defect | Status: new
Priority: major | Milestone:
On Fri, Mar 25, 2016 at 5:18 AM, Martin Landa
wrote:
>
> Please try to solve issues mentioned [2] ASAP.
More importantly, see blockers [3]. Note that the query was for 7.0.2 and
it requires to be updated after each release [4].
[2] https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.0.4tobebackp
Hi,
2016-03-25 14:01 GMT+01:00 Vaclav Petras :
>> These 4 all appear to be new features, not a bug fixes. If that is the
>> case, they should not be backported.
Ok, removed these issue from trac page. Martin
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
_
On Fri, Mar 25, 2016 at 8:02 AM, Moritz Lennert <
mlenn...@club.worldonline.be> wrote:
>
> These 4 all appear to be new features, not a bug fixes. If that is the
> case, they should not be backported.
+1
___
grass-dev mailing list
grass-dev@lists.osge
On Fri, Mar 25, 2016 at 8:46 AM, massimo di stefano <
massimodisa...@gmail.com> wrote:
> Or design the gui code base in a way that will make the adoption of new
> rendering systems as easy as possible.
>
+1. High quality code should be the main focus here.
___
Hi Anna,
Depending on how much effort the implementation in Qt of the current rendering
system will require
maybe is worth to explore new rendering tools.
Or design the gui code base in a way that will make the adoption of new
rendering systems as easy as possible.
It is my understanding that
#2270: t.list.rast where <=/>=
--+
Reporter: martinl | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: Temporal |Version: unspecified
Resolution
Bo,
I've read through your application. It is quite long, so I think you can
shorten the overview of the different algorithms a bit.
Maybe I was, again, unclear in my previous mails, but I would qualify
mean-shift and watershed as top-down algorithms. If your not comfortable
with these notio
On 25/03/16 10:18, Martin Landa wrote:
Hi,
based on [1] I would suggest to start "Soft freeze of release branch"
of releasebranch_7_0. Please try to solve issues mentioned [2]
r66382 + r66383: display/d.rast.arrow/ - Drainage aspect type
r66467: raster/r.random.cells expanded
r67007: vector/v
On 25/03/16 09:58, Markus Neteler wrote:
On Fri, Mar 25, 2016 at 9:03 AM, Martin Landa wrote:
Do you have any comments? Do you think that we are able to release
7.2/7.1 based on this timeline? Thanks, Martin
Yes, time to get 7.2 out.
+1
Moritz
_
Hi,
based on [1] I would suggest to start "Soft freeze of release branch"
of releasebranch_7_0. Please try to solve issues mentioned [2] ASAP.
Thanks! Martin
[1] https://trac.osgeo.org/grass/wiki/RFC/4_ReleaseProcedure
[2] https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.0.4tobebackported
--
Dear Bo,
Thanks for the document. I have to give classes now, but will try to
read while the students work ;-)
Apparently, I was not concentrating while writing some of my mails:
split-window is not a segmentation algorithm. Sorry about that. I meant
general (top-down) image splitting algori
On Fri, Mar 25, 2016 at 9:03 AM, Martin Landa wrote:
> Hi all,
>
> based on roadmap [1] we are planning to release 7.0.4 at the end of
> April
Maybe we could even anticipate that as soon as the few blockers are solved.
> and 7.2 (aka 7.1.0) somehow in June/July. It would mean to
> create in the
#2456: read CSV from GDAL data directory
-+-
Reporter: martinl | Owner: grass-dev@…
Type: task| Status: new
Priority: blocker | Milestone: 7.1.0
Component: Projections
Hi all,
based on roadmap [1] we are planning to release 7.0.4 at the end of
April and 7.2 (aka 7.1.0) somehow in June/July. It would mean to
create in the beginning of May (two months before release) new
releasebranch_7_2 (I know we discussed 7.1 vs. 7.2 release version
without any decision, let's
Hi,
2016-03-25 8:54 GMT+01:00 Pietro :
> Indeed there were no discussion, feel free to revert.
>
> I'm still confused... when can I break the trunk branch? :-)
personally I would wait with such changes to the moment when we will
create releasebranch_7_2 (two months before planning 7.2. release. F
Hi Martin,
On Fri, Mar 25, 2016 at 8:49 AM, Martin Landa wrote:
> I missed any discussion on ML. Such heavy changes should be discussed
> in advanced (probably I just missed it). Another question is if to
> backport such changes to relbr70. Our policy say only bugfixes. On the
> other hand, with
36 matches
Mail list logo
