Re: [GRASS-dev] planning grass 7.0.0beta4
On Mon, Dec 22, 2014 at 9:25 AM, Markus Neteler wrote: > Hi devs, > > after having spent many hours on > http://trac.osgeo.org/grass/ticket/2409 I'll tag beta4 later today. Here the improvement: from 48% of success back to 88% of success: http://fatra.cnr.ncsu.edu/grassgistests/summary_report/nc/files_percent_plot.png (see right end of graph) The remaining issues are, as outlined in my email from Saturday - related to missing maps on the test server - some Python/PyGRASS definition bugs. Tagging beta4 now... Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
Hi devs, after having spent many hours on http://trac.osgeo.org/grass/ticket/2409 I'll tag beta4 later today. Then we can release RC1 by end of the year. Best Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
Hi, 2014-12-19 10:58 GMT+01:00 Markus Neteler : > later today (hopefully) the backport of "raster_3d" element name will done in r63617. Martin -- Martin Landa http://geo.fsv.cvut.cz/gwiki/Landa http://gismentors.eu/mentors/landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
Hi devs, later today (hopefully) the backport of "raster_3d" element name will be done, i.e. we are ready for GRASS GIS 7.0.0beta4 (see also http://trac.osgeo.org/grass/wiki/Grass7Planning#Planningongoing). Shortly, before end of the year we can then release RC1. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
Hi, 2014-11-26 14:33 GMT+01:00 Markus Neteler : > On Sun, Nov 23, 2014 at 12:54 AM, Sören Gebbert > wrote: >> Backport done in r62858 - r62867. >> I hope everything works fine. > > Great, thanks for your efforts! Actually, all the work, including writing the manual pages, was sponsored by Otto Dassau [1]. I do not have enough spare time to do this. >> It would be great if we could automatically test all the changes that >> i have introduced in the release branch using the testsuite. > > Do you mean "online" on a server? Nope, just on the command line while implementing and backporting. Best regards Soeren [1] http://www.gbd-consult.de/ ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
On Wed, Nov 26, 2014 at 2:48 PM, Moritz Lennert wrote: > On 26/11/14 14:33, Markus Neteler wrote: >> >> On Sun, Nov 23, 2014 at 12:54 AM, Sören Gebbert >> wrote: >>> >>> Backport done in r62858 - r62867. >>> I hope everything works fine. >> >> >> Great, thanks for your efforts! >> >>> It would be great if we could automatically test all the changes that >>> i have introduced in the release branch using the testsuite. >> >> >> Do you mean "online" on a server? >> >>> A "make distclean" is needed. >> >> >> Martin is currently going through the parameters for >> http://trac.osgeo.org/grass/ticket/2409 >> >> Then we might be ready for beta4 by end of this week. > > > I still think that #2439 (and its duplicate #2476) is an almost blocker. > Digitization is a fundamental tool and these crashes render it almost > unusable for the normal(uninformed) user. The fix in r63077 needs to be tested and, in case, backported. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
On Wed, Nov 26, 2014 at 8:33 AM, Markus Neteler wrote: > > It would be great if we could automatically test all the changes that > > i have introduced in the release branch using the testsuite. > > Do you mean "online" on a server? I believe Soeren means by running the tests (in any way) as opposed to running some commands manually. There is no point in waiting for some server to run the tests the next day when you can run them yourself before the commit. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
On Wed, Nov 26, 2014 at 8:48 AM, Moritz Lennert < mlenn...@club.worldonline.be> wrote: > On 26/11/14 14:33, Markus Neteler wrote: > >> On Sun, Nov 23, 2014 at 12:54 AM, Sören Gebbert >> wrote: >> >>> Backport done in r62858 - r62867. >>> I hope everything works fine. >>> >> >> Great, thanks for your efforts! >> >> It would be great if we could automatically test all the changes that >>> i have introduced in the release branch using the testsuite. >>> >> >> Do you mean "online" on a server? >> >> A "make distclean" is needed. >>> >> >> Martin is currently going through the parameters for >> http://trac.osgeo.org/grass/ticket/2409 >> >> Then we might be ready for beta4 by end of this week. >> > > I still think that #2439 (and its duplicate #2476) is an almost blocker. > Digitization is a fundamental tool and these crashes render it almost > unusable for the normal(uninformed) user. > > Anyone out there with sufficient knowlege of GUI and vector code to check > this ? I tried but failed, I don't understand the vector library structures enough. As far as I remember, I identified the place where it crashes, if that helps. So probably either Martin or Markus Metz would be able to fix it. Anna > > Moritz > > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-dev > ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
On 26/11/14 14:33, Markus Neteler wrote: On Sun, Nov 23, 2014 at 12:54 AM, Sören Gebbert wrote: Backport done in r62858 - r62867. I hope everything works fine. Great, thanks for your efforts! It would be great if we could automatically test all the changes that i have introduced in the release branch using the testsuite. Do you mean "online" on a server? A "make distclean" is needed. Martin is currently going through the parameters for http://trac.osgeo.org/grass/ticket/2409 Then we might be ready for beta4 by end of this week. I still think that #2439 (and its duplicate #2476) is an almost blocker. Digitization is a fundamental tool and these crashes render it almost unusable for the normal(uninformed) user. Anyone out there with sufficient knowlege of GUI and vector code to check this ? Moritz ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
On Sun, Nov 23, 2014 at 12:54 AM, Sören Gebbert wrote: > Backport done in r62858 - r62867. > I hope everything works fine. Great, thanks for your efforts! > It would be great if we could automatically test all the changes that > i have introduced in the release branch using the testsuite. Do you mean "online" on a server? > A "make distclean" is needed. Martin is currently going through the parameters for http://trac.osgeo.org/grass/ticket/2409 Then we might be ready for beta4 by end of this week. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
Backport done in r62858 - r62867. I hope everything works fine. It would be great if we could automatically test all the changes that i have introduced in the release branch using the testsuite. A "make distclean" is needed. Best regards Soeren 2014-11-20 23:40 GMT+01:00 Sören Gebbert : > 2014-11-20 23:18 GMT+01:00 Markus Neteler : >> Hi, >> >> On Fri, Nov 14, 2014 at 4:31 PM, Markus Neteler wrote: >>> Hi all, >>> >>> http://trac.osgeo.org/grass/wiki/Grass7Planning#Planningongoing >>> >>> the only (?) remaining outstanding missing backport is the temporal >>> framework... >>> What do you plan, Soeren? > > Oh, uh, no, i missed that. So the testsuite has been backported as well? > >> >> for the time being I have updated the temporal manual with a selective >> sync to trunk in r62842. >> >> Probably that's it for beta4? Time flies.. > > I will start backporting tomorrow, probably all changes, since most of > them are tested using the test suite. > > Best regards > Soeren > >> >> Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
It would be great to get this out before the end of the year. I’m hoping to test a fix for r.random.surface today 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 Nov 20, 2014, at 9:04 PM, mailto:grass-dev-requ...@lists.osgeo.org>> mailto:grass-dev-requ...@lists.osgeo.org>> wrote: From: Markus Neteler mailto:nete...@osgeo.org>> Subject: Re: [GRASS-dev] planning grass 7.0.0beta4 Date: November 20, 2014 at 3:18:10 PM MST To: GRASS-dev mailto:grass-dev@lists.osgeo.org>>, Soeren Gebbert mailto:soerengebb...@googlemail.com>> Hi, On Fri, Nov 14, 2014 at 4:31 PM, Markus Neteler mailto:nete...@osgeo.org>> wrote: Hi all, http://trac.osgeo.org/grass/wiki/Grass7Planning#Planningongoing the only (?) remaining outstanding missing backport is the temporal framework... What do you plan, Soeren? for the time being I have updated the temporal manual with a selective sync to trunk in r62842. Probably that's it for beta4? Time flies.. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
On Thu, Nov 20, 2014 at 5:40 PM, Sören Gebbert wrote: > since most of > them are tested using the test suite. > There are three tests failing. One of them is slightly mystified by strange r3.univar output (none in fact). The other is shell script. http://fatra.cnr.ncsu.edu/grassgistests/reports_for_date-2014-11-20-08-00/report_for_nc_spm_08_grass7_nc/temporal/t.rast.to.rast3/test_strds_to_rast3/index.html http://fatra.cnr.ncsu.edu/grassgistests/reports_for_date-2014-11-20-08-00/report_for_nc_spm_08_grass7_nc/temporal/t.rast.algebra/test_raster_algebra_granularity/index.html http://fatra.cnr.ncsu.edu/grassgistests/reports_for_date-2014-11-20-08-00/report_for_nc_spm_08_grass7_nc/temporal/t.rast.accumulate/test.t.rast.accumulate/index.html But anyway, temporal framework is probably the most (automatic) test covered part of GRASS. I'm still not sure about the backport. I was not able to work on some things such as Python 2.6 support yet. Perhaps target for RC1 rather than beta4? ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
2014-11-20 23:18 GMT+01:00 Markus Neteler : > Hi, > > On Fri, Nov 14, 2014 at 4:31 PM, Markus Neteler wrote: >> Hi all, >> >> http://trac.osgeo.org/grass/wiki/Grass7Planning#Planningongoing >> >> the only (?) remaining outstanding missing backport is the temporal >> framework... >> What do you plan, Soeren? Oh, uh, no, i missed that. So the testsuite has been backported as well? > > for the time being I have updated the temporal manual with a selective > sync to trunk in r62842. > > Probably that's it for beta4? Time flies.. I will start backporting tomorrow, probably all changes, since most of them are tested using the test suite. Best regards Soeren > > Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
Hi, On Fri, Nov 14, 2014 at 4:31 PM, Markus Neteler wrote: > Hi all, > > http://trac.osgeo.org/grass/wiki/Grass7Planning#Planningongoing > > the only (?) remaining outstanding missing backport is the temporal > framework... > What do you plan, Soeren? for the time being I have updated the temporal manual with a selective sync to trunk in r62842. Probably that's it for beta4? Time flies.. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
Hi all, http://trac.osgeo.org/grass/wiki/Grass7Planning#Planningongoing the only (?) remaining outstanding missing backport is the temporal framework... What do you plan, Soeren? thanks Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
On 11 November 2014 22:13, Markus Neteler wrote: > On Tue, Nov 11, 2014 at 4:19 PM, Luca Delucchi wrote: >> Hi devs, >> >> On 6 November 2014 05:45, Anna Petrášová wrote: >>> >>> >>> Luca, are you or anyone else planning to do that? >>> >> >> I'm going to backport all the python sphinx documentation, bot for >> lib/python than gui/wxpython. >> It's really a lot of changes. I spent several hours to try to backport >> only the right stuff. > > Well done, Luca! Have have generated the docs (anticipated the > Saturday cronjob): > http://grass.osgeo.org/grass70/manuals/libpython/ > Ok I found a small problem in the index there is this line "Testing GRASS GIS source code and modules: (gunittest package" but in GRASS 7.0 there is not gunittest package. I don't understand if gunittest will be backported before 7.0 release, if we backport we can leave that line, otherwise it should be removed > >> I didn't backport: >> - the temporal documentation and some changes related to it >> - something related to g.gui.rlisetup because I have to commit to some >> changes in trunk before >> - gunnintest docs and several test. > > Also some Python lib differences are yet there. > yes something... > Markus -- ciao Luca http://gis.cri.fmach.it/delucchi/ www.lucadelu.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
On Tue, Nov 11, 2014 at 4:19 PM, Luca Delucchi wrote: > Hi devs, > > On 6 November 2014 05:45, Anna Petrášová wrote: >> >> >> Luca, are you or anyone else planning to do that? >> > > I'm going to backport all the python sphinx documentation, bot for > lib/python than gui/wxpython. > It's really a lot of changes. I spent several hours to try to backport > only the right stuff. Well done, Luca! Have have generated the docs (anticipated the Saturday cronjob): http://grass.osgeo.org/grass70/manuals/libpython/ > I didn't backport: > - the temporal documentation and some changes related to it > - something related to g.gui.rlisetup because I have to commit to some > changes in trunk before > - gunnintest docs and several test. Also some Python lib differences are yet there. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
Hi devs, On 6 November 2014 05:45, Anna Petrášová wrote: > > > Luca, are you or anyone else planning to do that? > I'm going to backport all the python sphinx documentation, bot for lib/python than gui/wxpython. It's really a lot of changes. I spent several hours to try to backport only the right stuff. I didn't backport: - the temporal documentation and some changes related to it - something related to g.gui.rlisetup because I have to commit to some changes in trunk before - gunnintest docs and several test. -- ciao Luca http://gis.cri.fmach.it/delucchi/ www.lucadelu.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
On Mon, Nov 10, 2014 at 8:51 AM, Moritz Lennert wrote: > On 08/11/14 22:44, Markus Neteler wrote: >> >> Hi, >> >> to better coordinate the missing items for the upcoming beta4 release, >> I have added a list at >> >> http://trac.osgeo.org/grass/wiki/Grass7Planning#Planningongoing >> --> Beta 4 release (TODOs): being planned as last beta before RC1 >> >> Please check (and update). > > > "temporal GIS backport to relbranch70 " > > Is this really something we want to do in a beta4 stage ? Yes of course. At least partially since we cannot change the user interface later nor rename modules or remove some. Otherwise we'll see this in GRASS GIS 8 only. > AFAICT, the new version has not been tested extensively, or ? That's what the beta is for. Additionally there is a blocker bug open about where the temporal DB goes. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
On 08/11/14 22:44, Markus Neteler wrote: Hi, to better coordinate the missing items for the upcoming beta4 release, I have added a list at http://trac.osgeo.org/grass/wiki/Grass7Planning#Planningongoing --> Beta 4 release (TODOs): being planned as last beta before RC1 Please check (and update). "temporal GIS backport to relbranch70 " Is this really something we want to do in a beta4 stage ? AFAICT, the new version has not been tested extensively, or ? Moritz ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
Hi, to better coordinate the missing items for the upcoming beta4 release, I have added a list at http://trac.osgeo.org/grass/wiki/Grass7Planning#Planningongoing --> Beta 4 release (TODOs): being planned as last beta before RC1 Please check (and update). Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
On Sun, Nov 2, 2014 at 5:08 PM, Moritz Lennert wrote: > On 02/11/14 20:36, Markus Neteler wrote: > >> Hi, >> >> concerning the upcoming beta4 release, it would be nice to have >> >> - python docs backport (Sphinx) >> > Luca, are you or anyone else planning to do that? > - finish dead code cleanup >> (http://grasswiki.osgeo.org/wiki/GRASS_7_ideas_collection# >> Dead_code_cleanup) >> - temporal GIS re-sync (?) >> - anything else? >> > > Yes, I think that #2439 (g.gui.iclass / wxdigit crashes) needs to be > solved before we ship grass7.0. and some more feedback on Glynn's suggestion to re-examine how floating-point values are converted to integers in fpreclass.c and put_row.c would be appreciated... http://trac.osgeo.org/grass/ticket/2053#comment:8 Anna > > Moritz > > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-dev > ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
On 02/11/14 20:36, Markus Neteler wrote: Hi, concerning the upcoming beta4 release, it would be nice to have - python docs backport (Sphinx) - finish dead code cleanup (http://grasswiki.osgeo.org/wiki/GRASS_7_ideas_collection#Dead_code_cleanup) - temporal GIS re-sync (?) - anything else? Yes, I think that #2439 (g.gui.iclass / wxdigit crashes) needs to be solved before we ship grass7.0. Moritz ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
On Sun, Nov 2, 2014 at 2:36 PM, Markus Neteler wrote: > - anything else? #2326 needs to be solved. It's originally major but the solution we agreed on with Glynn makes it a clear blocker because it changes API. The reason why it changes API is that the API was purely designed. We need to change it before 7.0, so that people can start using the right interface. The challenging part is affected code in GRASS GIS [2]. There is a lot of changes required and there is no chance we can test all before (without) releasing new version because the test coverage is very low. [1] http://trac.osgeo.org/grass/ticket/2326 [2] http://trac.osgeo.org/grass/ticket/2326#comment:5 ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
Hi, concerning the upcoming beta4 release, it would be nice to have - python docs backport (Sphinx) - finish dead code cleanup (http://grasswiki.osgeo.org/wiki/GRASS_7_ideas_collection#Dead_code_cleanup) - temporal GIS re-sync (?) - anything else? Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
Hi Vaclav, On Tue, Oct 28, 2014 at 4:09 AM, Vaclav Petras wrote: > On Sun, Oct 26, 2014 at 7:22 AM, Martin Landa > wrote: >> it's long time ago when GRASS 7.0.0beta3 has been published (more then >> two months ago). I would suggest to publish beta4, what do you think? >> Is there any blocker or something which should be finished (e.g. >> g.list/g.remove backports)? > > I was working on #2326 a little bit last week but I'm far from finishing. I > have a first implementation of raise in run/write/read command functions and > some changes make GUI start again. Nothing done on the rest of the code. Thanks for that! > A branch would be helpful for this, by the way. yes, I also think that a branch would be useful... Do all the changes that we need to do in one big commit it seems unfeasible, and without a branch it is quite difficult to share and work as a team... So have some branches with a very precise scope like: #2326 or make GRASS compatible with python3 that can be reach in a short time (2 weeks/ 1 month), should allow us to broke GRASS without the fear of bothering other users/developers until we reach a pretty stable code that can be included to trunk. IMO these branches should be automatically synchronized with trunk and have a responsible to manage/handle the conflict that could raise from the merging process. [OT] I think git/github could make these things easier... > We've been also discussing removing things from __init__.py files. I'm not > sure if we should apply this but we probably should replace the practice > > import grass.script as grass +1 It has always looked weird to me. > by something more reasonable, explicit imports of things or > > import grass.script as gscript > > or > > import grass.script.core as gcore > import grass.script.core as gscore +1 Pietro ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
On Sun, Oct 26, 2014 at 7:22 AM, Martin Landa wrote: > Hi all, > > it's long time ago when GRASS 7.0.0beta3 has been published (more then > two months ago). I would suggest to publish beta4, what do you think? > Is there any blocker or something which should be finished (e.g. > g.list/g.remove backports)? > > Hi, I was working on #2326 a little bit last week but I'm far from finishing. I have a first implementation of raise in run/write/read command functions and some changes make GUI start again. Nothing done on the rest of the code. A branch would be helpful for this, by the way. We've been also discussing removing things from __init__.py files. I'm not sure if we should apply this but we probably should replace the practice import grass.script as grass by something more reasonable, explicit imports of things or import grass.script as gscript or import grass.script.core as gcore import grass.script.core as gscore Depending on what we consider more stable or nier and if we will empty __init__.py. Vaclav http://trac.osgeo.org/grass/ticket/2326 > Cheers, Martin > > -- > Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa * > http://www.gismentors.eu/mentors/landa > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-dev > ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
Hi, On Sun, Oct 26, 2014 at 9:50 PM, Markus Neteler wrote: > On Sun, Oct 26, 2014 at 9:05 PM, Martin Landa wrote: >> 2014-10-26 17:51 GMT+01:00 Markus Neteler : >>> -the python API back port >> >> it seems to be done by Pietro in r62382. Martin > > That is a part - it needs to include the Sphinx docs as well. Happy to > help, we just need to coordinate the efforts. I tried to close the gap between the pygrass version in trunk and in release candidate, now they are at the same level. I agree with you, we should backport also the sphinx docs. > PS: I was wondering about a partial bulk backport here, see > https://stackoverflow.com/questions/4547142/svn-automate-merge-of-trunk-into-branch I think that this option could be extremely helpful when/if we will make a python3 branch of GRASS. Pietro ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
On Sun, Oct 26, 2014 at 12:51 PM, Markus Neteler wrote: > > On Oct 26, 2014 12:22 PM, "Martin Landa" wrote: > > > > Hi all, > > > > it's long time ago when GRASS 7.0.0beta3 has been published (more then > > two months ago). I would suggest to publish beta4, what do you think? > > Is there any blocker or something which should be finished (e.g. > > g.list/g.remove backports)? > > There are two important blockers: > - the g.list etc backport > I backported g.remove/g.list in r62393 and r62396. Best, Huidae > -the python API back port > > Ciao > Markus > > > Cheers, Martin > > > > -- > > Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa * > > http://www.gismentors.eu/mentors/landa > > ___ > > grass-dev mailing list > > grass-dev@lists.osgeo.org > > http://lists.osgeo.org/mailman/listinfo/grass-dev > > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-dev > ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
On Sun, Oct 26, 2014 at 9:05 PM, Martin Landa wrote: > 2014-10-26 17:51 GMT+01:00 Markus Neteler : >> -the python API back port > > it seems to be done by Pietro in r62382. Martin That is a part - it needs to include the Sphinx docs as well. Happy to help, we just need to coordinate the efforts. Markus PS: I was wondering about a partial bulk backport here, see https://stackoverflow.com/questions/4547142/svn-automate-merge-of-trunk-into-branch ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
On Sun, Oct 26, 2014 at 5:51 PM, Markus Neteler wrote: > On Oct 26, 2014 12:22 PM, "Martin Landa" wrote: > There are two important blockers: > - the g.list etc backport > - the python API back port ... additionally also the .po files to be done. I can do that as soon as the python API backport is settled... Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
Hi, 2014-10-26 17:51 GMT+01:00 Markus Neteler : > There are two important blockers: > - the g.list etc backport OK > -the python API back port it seems to be done by Pietro in r62382. Martin -- Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa * http://www.gismentors.eu/mentors/landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] planning grass 7.0.0beta4
On Oct 26, 2014 12:22 PM, "Martin Landa" wrote: > > Hi all, > > it's long time ago when GRASS 7.0.0beta3 has been published (more then > two months ago). I would suggest to publish beta4, what do you think? > Is there any blocker or something which should be finished (e.g. > g.list/g.remove backports)? There are two important blockers: - the g.list etc backport -the python API back port Ciao Markus > Cheers, Martin > > -- > Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa * > http://www.gismentors.eu/mentors/landa > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
