Re: [GRASS-dev] 6.4.4 planning
Hi devs, -- yet inofficial note -- the final GRASS GIS 6.4.4 release has been published: https://trac.osgeo.org/grass/wiki/Release/6.4.4-News To be done: - create binaries (will notify the packagers later today) - update CMS - write announcement - publish it officially best Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
On Wed, Jun 18, 2014 at 12:34 AM, Martin Landa wrote: > Hi, > > 2014-06-17 19:54 GMT+02:00 Markus Neteler : >>> Needs improvement: >>> http://trac.osgeo.org/grass/wiki/Release/6.4.4RC1-News >> >> ... also a volunteer is seeked who scans the updates in the post-6.4.3 >> ChangeLog and merges them into above trac page. > > I went through svn log and tried to updated trac accordingly. Thanks for this job! > Part of > the log messages were very *cryptic*, PLEASE COMITTERS, TRY TO WRITE > YOUR LOGS IN READABLE WAY (TO BE REUSED FOR NEWS), ie. "name of > module/library: description (possible trac ticket or merge commit). > THANKS. +1 Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
Hi, 2014-06-17 19:54 GMT+02:00 Markus Neteler : >> Needs improvement: >> http://trac.osgeo.org/grass/wiki/Release/6.4.4RC1-News > > ... also a volunteer is seeked who scans the updates in the post-6.4.3 > ChangeLog and merges them into above trac page. I went through svn log and tried to updated trac accordingly. Part of the log messages were very *cryptic*, PLEASE COMITTERS, TRY TO WRITE YOUR LOGS IN READABLE WAY (TO BE REUSED FOR NEWS), ie. "name of module/library: description (possible trac ticket or merge commit). THANKS. Martin -- Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
On Sat, Jun 14, 2014 at 3:20 PM, Markus Neteler wrote: > On Fri, Jun 13, 2014 at 4:47 PM, Markus Neteler wrote: >> I'll try to do prepare RC1 later today or tomorrow. > > I have done the tagging: release_20140614_grass_6_4_4RC1 > > Needs improvement: > http://trac.osgeo.org/grass/wiki/Release/6.4.4RC1-News ... also a volunteer is seeked who scans the updates in the post-6.4.3 ChangeLog and merges them into above trac page. Markus > All the other news and CMS updates (will do later) + binary > complilations need to be done, too. > > Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
Hi Markus, 2014-06-14 15:20 GMT+02:00 Markus Neteler : > On Fri, Jun 13, 2014 at 4:47 PM, Markus Neteler wrote: >> I'll try to do prepare RC1 later today or tomorrow. > > I have done the tagging: release_20140614_grass_6_4_4RC1 > > Needs improvement: > http://trac.osgeo.org/grass/wiki/Release/6.4.4RC1-News > > All the other news and CMS updates (will do later) + binary > complilations need to be done, too. thanks! Binaries for Windows are online (32bit only) - both standalone [1] and osgeo4w. Thanks for testing in advance! Martin [1] http://grass.osgeo.org/grass64/binary/mswindows/native/WinGRASS-6.4.4RC1-1-Setup.exe -- Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
On Fri, Jun 13, 2014 at 4:47 PM, Markus Neteler wrote: > I'll try to do prepare RC1 later today or tomorrow. I have done the tagging: release_20140614_grass_6_4_4RC1 Needs improvement: http://trac.osgeo.org/grass/wiki/Release/6.4.4RC1-News All the other news and CMS updates (will do later) + binary complilations need to be done, too. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
On Fri, Jun 13, 2014 at 1:10 PM, Moritz Lennert wrote: ... > I'm not standing in your way, especially in light of the limited time we all > seem to have. I'll try to do prepare RC1 later today or tomorrow. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
On 12/06/14 22:20, Markus Neteler wrote: On Thu, Jun 12, 2014 at 9:20 AM, Moritz Lennert wrote: On 12/06/14 00:15, Markus Neteler wrote: [...] I'll wait for Moritz' ok since he objected to let me tag it. I don't know where you got that idea from. I got that from email from you: --- On Mon, Jun 2, 2014 at 10:41 AM, Moritz Lennert I think (also in line with the above) a clear freeze announcement has to go out first to give a 24-48h warning to everyone. Then RC1 can be tagged. This says "I think" so is just a voicing of opinion, it's not a veto. If voicing a suggestion is seen as blocking progress, then that's a sad state of affairs. But let me do RC1 first :-) I'm not standing in your way, especially in light of the limited time we all seem to have. Moritz ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
Hi Moritz, all, On Thu, Jun 12, 2014 at 10:20 PM, Markus Neteler wrote: > On Thu, Jun 12, 2014 at 9:20 AM, Moritz Lennert ... >> if you had applied the proposed procedure when it was proposed [1], >> we would be really close to RC2 by now... If "you" means me: as pointed out I was travelling, now travelling again. I had time before when responses were slow. BTW: I forgot to mention that release management had a long been existing: http://grasswiki.osgeo.org/wiki/Category:Release_Roadmap - GRASS 6.1 Feature Plan - GRASS 6.2 Feature Plan - GRASS 6.3 Feature Plan - GRASS 6.4 Feature Plan --> http://trac.osgeo.org/grass/wiki/Grass6Planning As you see, nobody cared in the past 2 years. That's how it is. Or was? Of course I am happy to make a new attempt, maybe it works out nowadays. Best Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
On Thu, Jun 12, 2014 at 9:20 AM, Moritz Lennert wrote: > On 12/06/14 00:15, Markus Neteler wrote: >> >> On Wed, Jun 11, 2014 at 9:02 PM, Martin Landa >> wrote: >>> >>> 2014-06-10 23:15 GMT+02:00 Martin Landa : > > Personally I believe that getting-things-done is the better approach > for 6.4.4 RC1. Let's tag RC1, otherwise we stay on the same place for other days/weeks/months. >>> >>> >>> I think we can go ahead... Martin >> >> >> I'll wait for Moritz' ok since he objected to let me tag it. > > > I don't know where you got that idea from. I got that from email from you: --- On Mon, Jun 2, 2014 at 10:41 AM, Moritz Lennert wrote: > On 31/05/14 23:19, Markus Neteler wrote: >> On Mon, May 26, 2014 at 12:58 PM, Moritz Lennert ... >>> - RC1 beginning of next week >> >> Should that happen then? > > I think (also in line with the above) a clear freeze announcement has to go > out first to give a 24-48h warning to everyone. Then RC1 can be tagged. > > Sorry, but I won't be of much help these days as we've started exams here > and I'll be busy with that almost all week. --- ... it exceeded as I explained to you my available time window. Perhaps some people underestimate the amount of work to prepare a release, even a RC. So I just remind you that a bit more than just launching the "svn tag" is involved. And the number of broken releases in the past is close to zero. > I proposed a more structured process of doing it, that's all. ... which is generally fine. > Since this proposal has not met with any > concrete feedback, other than it shouldn't be applied for 6.4, I'll just get > out of the way and let you handle things the way you want to. We have 19 "virtual" full time developers according to ohloh. I cannot speak for the others but I want to get RC1 done since it is *only* a release candidate and nothing else. Then we can consider to even apply a new procedure. Just please let us do this RC1 - the planning accouncement is from mid of Nov 2013, so probably enough time ago. Surely I can retired from GRASS 6 maintenance if that opens up things. But let me do RC1 first :-) > Let me just add (gratuitously, I'm aware of that, but I'm a bit tired of a > process where people make clear and concrete suggestions on an issue, but > the content of these suggestions is just ignored, and the people who made > them are then blamed that nothing advances) that if you had applied the > proposed procedure when it was proposed [1], we would be really close to RC2 > by now... Yes, if more feedback would come I would be happy as well. Markus > Moritz > > [1] http://lists.osgeo.org/pipermail/grass-dev/2014-May/069126.html ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
On 12/06/14 00:15, Markus Neteler wrote: On Wed, Jun 11, 2014 at 9:02 PM, Martin Landa wrote: 2014-06-10 23:15 GMT+02:00 Martin Landa : Personally I believe that getting-things-done is the better approach for 6.4.4 RC1. Let's tag RC1, otherwise we stay on the same place for other days/weeks/months. I think we can go ahead... Martin I'll wait for Moritz' ok since he objected to let me tag it. I don't know where you got that idea from. I proposed a more structured process of doing it, that's all. Since this proposal has not met with any concrete feedback, other than it shouldn't be applied for 6.4, I'll just get out of the way and let you handle things the way you want to. Let me just add (gratuitously, I'm aware of that, but I'm a bit tired of a process where people make clear and concrete suggestions on an issue, but the content of these suggestions is just ignored, and the people who made them are then blamed that nothing advances) that if you had applied the proposed procedure when it was proposed [1], we would be really close to RC2 by now... Moritz [1] http://lists.osgeo.org/pipermail/grass-dev/2014-May/069126.html ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
On Wed, Jun 11, 2014 at 9:02 PM, Martin Landa wrote: > 2014-06-10 23:15 GMT+02:00 Martin Landa : >>> Personally I believe that getting-things-done is the better approach >>> for 6.4.4 RC1. >> >> Let's tag RC1, otherwise we stay on the same place for other >> days/weeks/months. > > I think we can go ahead... Martin I'll wait for Moritz' ok since he objected to let me tag it. Markus (offline on Thursday) ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
2014-06-10 23:15 GMT+02:00 Martin Landa : >> Personally I believe that getting-things-done is the better approach >> for 6.4.4 RC1. > > Let's tag RC1, otherwise we stay on the same place for other > days/weeks/months. I think we can go ahead... Martin -- Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
2014-06-11 11:29 GMT+02:00 Moritz Lennert : > I did not say without defined timeline within the process, but not > fixed-date. IOW, if we want to keep up a minimum with the reputation of ah, OK. Martin -- Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
On 11/06/14 10:30, Martin Landa wrote: Hi, 2014-06-11 10:01 GMT+02:00 Moritz Lennert : I still believe that such a more clearly defined process (and again, I'm _not_ speaking about fixed-date releases) would help, but apparently I'm the could you please explain a bit, how do you want to set up clear release process without defined timeline? I did not say without defined timeline within the process, but not fixed-date. IOW, if we want to keep up a minimum with the reputation of fairly stable software, I don't think that for a project such as GRASS it would be a good idea to say "we'll have a release every six months, one in January and one in July". Rather, I think that to avoid the discussions we've had concerning which types of code modifications should go into a specific branch at which times and who decides what goes in and what does not, we should define the procedure more clearly. This also includes a clear calendar of the process itself. I'll draft an RFC. Moritz ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
Hi, 2014-06-11 10:01 GMT+02:00 Moritz Lennert : > I still believe that such a more clearly defined process (and again, I'm > _not_ speaking about fixed-date releases) would help, but apparently I'm the could you please explain a bit, how do you want to set up clear release process without defined timeline? > only one who thinks so. You are not the only one, but it takes some time to discuss and set up (ideally as RFC). So it's topic for GRASS 7 not GRASS 6, thats all. Martin -- Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
On 10/06/14 23:07, Markus Neteler wrote: On Tue, Jun 10, 2014 at 10:12 PM, Vaclav Petras wrote: ... And back to the main topic, I'm bit lost in 6.4 releasing, is something blocking the release? (Except for limited time Markus have for it.) I had enough time in the past two weeks. The blocker is the wish of Moritz to start a full announcement cycle of dealing with the release management which has been historically ignored. Also his suggestion has been ignored so far, not giving much hope for a real one. I never intended for my suggestion to be a blocker. I had hoped it would help apease the conflicts that seemed to arise around the 6.4.4 release. I still believe that such a more clearly defined process (and again, I'm _not_ speaking about fixed-date releases) would help, but apparently I'm the only one who thinks so. Moritz ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
> And back to the main topic, I'm bit lost in 6.4 releasing, is something blocking the release? as there are no blockers, the most simple thing is just tag and prepare RC1 let the nice work of coding into the wild. - best regards Helmut -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Re-6-4-4-planning-tp5094052p5145171.html Sent from the Grass - Dev mailing list archive at Nabble.com. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
Hi, 2014-06-10 23:29 GMT+02:00 Vaclav Petras : > For me email with "6.4.4*planning" was the announcement of the current one. > We for sure want some fixed time-based release cycle for 7 but there is no > reason to not release if it is ready just because of missing policy (there > will be next release soon, right? so you everybody can push his changes > there). I complete agree, lets tag 6.4.4RC1 today/tomorrow. Martin -- Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
On Tue, Jun 10, 2014 at 5:15 PM, Martin Landa wrote: > 2014-06-10 23:07 GMT+02:00 Markus Neteler : > > > The blocker is the wish of Moritz to start a full announcement cycle > > of dealing with the release management which has been historically > > ignored. Also his suggestion has been ignored so far, not giving much > > hope for a real one. > > That's completely unrealistic. We can start such procedure with G7 > (time-based release policy). > > > Personally I believe that getting-things-done is the better approach > > for 6.4.4 RC1. > > Let's tag RC1, otherwise we stay on the same place for other > days/weeks/months. > > For me email with "6.4.4*planning" was the announcement of the current one. We for sure want some fixed time-based release cycle for 7 but there is no reason to not release if it is ready just because of missing policy (there will be next release soon, right? so you everybody can push his changes there). Martin > > -- > Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa > ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
2014-06-10 23:07 GMT+02:00 Markus Neteler : > The blocker is the wish of Moritz to start a full announcement cycle > of dealing with the release management which has been historically > ignored. Also his suggestion has been ignored so far, not giving much > hope for a real one. That's completely unrealistic. We can start such procedure with G7 (time-based release policy). > Personally I believe that getting-things-done is the better approach > for 6.4.4 RC1. Let's tag RC1, otherwise we stay on the same place for other days/weeks/months. Martin -- Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
On Tue, Jun 10, 2014 at 10:12 PM, Vaclav Petras wrote: ... > And back to the main topic, I'm bit lost in 6.4 releasing, is something > blocking the release? (Except for limited time Markus have for it.) I had enough time in the past two weeks. The blocker is the wish of Moritz to start a full announcement cycle of dealing with the release management which has been historically ignored. Also his suggestion has been ignored so far, not giving much hope for a real one. Personally I believe that getting-things-done is the better approach for 6.4.4 RC1. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
On Tue, Jun 10, 2014 at 3:30 PM, Markus Neteler wrote: > > >> Please note ... the OSGeoLive feature freeze for the FOSS4G Portland > >> conf is upcoming. Would be a pity to not even see 6.4.4 therein! > > > > I'm a bit more available in the next weeks, so I can help with this > process. > > Just let me know. > > Unless we don't start tagging one day it will never reach the OSGeoLive > DVD. > Their freeze is the 6 July 2014 according to Cameron's email. And indeed > we need > to have GRASS 7 in it for our upcoming workshop but that's offtopic > for this email thread. It's off topic but that's actually a valid note. Do we aim on having 6.4 or 7.0 in next OSGeo Live. We cannot have both, in [Workshops] [Live-demo] OSGeoLive in FOSS4G 2014 workshops? http://lists.osgeo.org/pipermail/conference-workshops/2014-June/000538.html Cameron Shorter says: > To date we only have one version of each application installed on OSGeo-Live, and I don't think we should break that policy. > (We aim to ensure a clear and simple experience for new users). > So I think we should only have one version of GRASS installed. So 6.4 or 7.0. And this might be complication for QGIS GRASS plugin. And back to the main topic, I'm bit lost in 6.4 releasing, is something blocking the release? (Except for limited time Markus have for it.) Vaclav ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
On Tue, Jun 10, 2014 at 3:01 PM, Moritz Lennert wrote: > On 06/06/14 21:43, Markus Neteler wrote: >> >> On Thu, Jun 5, 2014 at 5:47 PM, Moritz Lennert >> wrote: >> ... >>> >>> As I've already told Markus off-list, I think that in order for this to >>> work >>> we would need a clearly defined release-process with clear announcements >>> of >>> the different steps (pre-freeze warning sufficiently early, freeze >>> announcement, pre-tag announcement, etc) and a strict respect of the >>> rules >>> during this process (i.e. no non bugfix commits during a freeze), etc. >> >> >> It doesn't seem to happen. [I referred to the lack of responses in a sarcastic way :-) ] > At this stage there have never been clear announcements, easily identifiable > as such for all developers. We should not assume that every developer reads > every thread. Thus, such announcements should be outside of existing > threads, and clearly marked in the subject. Sure. But I may mention that I do these releases since end of 1997 and any attempt in the past to implement a *respected* release schedule failed! See the archive for older attempts. >> Please note ... the OSGeoLive feature freeze for the FOSS4G Portland >> conf is upcoming. Would be a pity to not even see 6.4.4 therein! > > I'm a bit more available in the next weeks, so I can help with this process. > Just let me know. Unless we don't start tagging one day it will never reach the OSGeoLive DVD. Their freeze is the 6 July 2014 according to Cameron's email. And indeed we need to have GRASS 7 in it for our upcoming workshop but that's offtopic for this email thread. Markus (who feels a bit blocked by some developers) ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
On 06/06/14 21:43, Markus Neteler wrote: On Thu, Jun 5, 2014 at 5:47 PM, Moritz Lennert wrote: ... As I've already told Markus off-list, I think that in order for this to work we would need a clearly defined release-process with clear announcements of the different steps (pre-freeze warning sufficiently early, freeze announcement, pre-tag announcement, etc) and a strict respect of the rules during this process (i.e. no non bugfix commits during a freeze), etc. It doesn't seem to happen. At this stage there have never been clear announcements, easily identifiable as such for all developers. We should not assume that every developer reads every thread. Thus, such announcements should be outside of existing threads, and clearly marked in the subject. Please note ... the OSGeoLive feature freeze for the FOSS4G Portland conf is upcoming. Would be a pity to not even see 6.4.4 therein! I'm a bit more available in the next weeks, so I can help with this process. Just let me know. Moritz ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
On Thu, Jun 5, 2014 at 5:47 PM, Moritz Lennert wrote: ... > As I've already told Markus off-list, I think that in order for this to work > we would need a clearly defined release-process with clear announcements of > the different steps (pre-freeze warning sufficiently early, freeze > announcement, pre-tag announcement, etc) and a strict respect of the rules > during this process (i.e. no non bugfix commits during a freeze), etc. It doesn't seem to happen. Please note ... the OSGeoLive feature freeze for the FOSS4G Portland conf is upcoming. Would be a pity to not even see 6.4.4 therein! > I'm not convinced that a time-based release-policy is the solution, but I > think a more clearly defined release-process policy might help in avoiding > frustrations. So let's see then... Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
Hi, 2014-06-05 17:47 GMT+02:00 Moritz Lennert : [...] > As I've already told Markus off-list, I think that in order for this to work > we would need a clearly defined release-process with clear announcements of > the different steps (pre-freeze warning sufficiently early, freeze > announcement, pre-tag announcement, etc) and a strict respect of the rules > during this process (i.e. no non bugfix commits during a freeze), etc. > > I'm not convinced that a time-based release-policy is the solution, but I > think a more clearly defined release-process policy might help in avoiding > frustrations. right, let's push out 6.4.4 somehow, new release policy is question for G7... Martin -- Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
Hi Markus, 2014-06-05 9:56 GMT+02:00 Markus Neteler : > I would be able to tag RC1 tomorrow (Friday) if there are no objections. > > Are there any pending backports? I have some uncommitted fixes for > r.pack and v.external but will not commit them to avoid another > flamewar. :) no objection for my side. From other project (GDAL for example) I got feeling that RC period must be short. So e.g. RC2 or final one/two weeks after RC1 Also reporting bunch of blockers during RC stage can be interpreted as attempt to block release. I hope that for GRASS 7 will defined fixed time-based release policy with freeze stage (one/two months - ideal time for reporting blockers), than simply release and go on... Martin -- Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
hi all, I would be able to tag RC1 tomorrow (Friday) if there are no objections. Are there any pending backports? I have some uncommitted fixes for r.pack and v.external but will not commit them to avoid another flamewar. :) Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
On Mon, Jun 2, 2014 at 10:41 AM, Moritz Lennert wrote: > On 31/05/14 23:19, Markus Neteler wrote: >> >> On Mon, May 26, 2014 at 12:58 PM, Moritz Lennert >> wrote: >> ... >>> >>> - Real freeze of grass64_release at the end of this week. This means that >>> any backports from grass6_devel should happen before that moment. But >>> only >>> non-invasive and well-tested elements should be backported. >> >> >> Seems nothing got backported in the past week any more: >> http://trac.osgeo.org/grass/log/grass/branches/releasebranch_6_4 > > > At the same time, we did not officially announce the calendar (it was in a > reply to a long-going thread...). But let's hope all the interested people > saw the calendar. Yes. >>> - RC1 beginning of next week >> >> >> Should that happen then? > > > I think (also in line with the above) a clear freeze announcement has to go > out first to give a 24-48h warning to everyone. Then RC1 can be tagged. > > Sorry, but I won't be of much help these days as we've started exams here > and I'll be busy with that almost all week. So I'll wait... cheers Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
On 31/05/14 23:19, Markus Neteler wrote: On Mon, May 26, 2014 at 12:58 PM, Moritz Lennert wrote: ... - Real freeze of grass64_release at the end of this week. This means that any backports from grass6_devel should happen before that moment. But only non-invasive and well-tested elements should be backported. Seems nothing got backported in the past week any more: http://trac.osgeo.org/grass/log/grass/branches/releasebranch_6_4 At the same time, we did not officially announce the calendar (it was in a reply to a long-going thread...). But let's hope all the interested people saw the calendar. - RC1 beginning of next week Should that happen then? I think (also in line with the above) a clear freeze announcement has to go out first to give a 24-48h warning to everyone. Then RC1 can be tagged. Sorry, but I won't be of much help these days as we've started exams here and I'll be busy with that almost all week. Moritz ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
On Mon, May 26, 2014 at 12:58 PM, Moritz Lennert wrote: ... > - Real freeze of grass64_release at the end of this week. This means that > any backports from grass6_devel should happen before that moment. But only > non-invasive and well-tested elements should be backported. Seems nothing got backported in the past week any more: http://trac.osgeo.org/grass/log/grass/branches/releasebranch_6_4 > - RC1 beginning of next week Should that happen then? Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
Hi, 2014-05-26 12:58 GMT+02:00 Moritz Lennert : > I think we are not far at all from releasing, so maybe something like this: > > - Real freeze of grass64_release at the end of this week. This means that > any backports from grass6_devel should happen before that moment. But only > non-invasive and well-tested elements should be backported. > > - RC1 beginning of next week > > - Bug squashing effort during the two weeks that follow. > > - RC2 around June 15th. > > - Another week of bug squashing, if necessary. > > - Release of 6.4.4 by end of June, the latest. > > That sound ok ? > sounds good to me... Martin -- Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
On 25/05/14 09:32, Markus Neteler wrote: On Fri, May 16, 2014 at 2:38 PM, Moritz Lennert wrote: On 15/05/14 23:14, Markus Neteler wrote: ... Draft announcement to be updated: http://trac.osgeo.org/grass/wiki/Release/6.4.4RC1-News "Important bugs concerning the next release" https://trac.osgeo.org/grass/report/13 Here the full list of issues but none is a blocker: https://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&group=status&milestone=6.4.4 To test on Windows: g.remove cannot remove vector map because of space in DB layer name https://trac.osgeo.org/grass/ticket/1438 You note that this should be wontfix. What do you want to be tested ? Right, nothing to be tested I guess. To be closed? Yes. - r.walk backport https://trac.osgeo.org/grass/ticket/1628 ... not sure what to backport. Markus Metz may have an idea. v.kcv backport https://trac.osgeo.org/grass/ticket/2035 See my comment in the ticket. The vector overwrite issue in other mapsets seems to be a general problem, see ticket. Yes, and I think this is serious enough to solve this before release, even if people seem to have lived with it for a long time... And/or I can tag RC1 now and we do these issues later. I think that except for the r.walk segfault, none are really showstoppers. And even that only seems to be reproducible in a very specific situation. Given the recent discussion elsewhere I am stuck here. Do you want me to tag RC1 or wait ...? I think that we should try to structure the entire release process a bit more as we are currently dealing with two release processes in parallel (6 and 7) and I have the feeling that this is a bit overwhelming for our little team and that the lack of clear structure of the process leads to the frustrations seen on the list lately. I would, therefore, propose to focus on 6.4.4 for now, getting that out of the door before we work on 7.0 (especially since there seem to be some fundamental issues to be solved before releasing anything). I also think that we should work out a clear calendar for that release with official announcements of freeze policy. I think we are not far at all from releasing, so maybe something like this: - Real freeze of grass64_release at the end of this week. This means that any backports from grass6_devel should happen before that moment. But only non-invasive and well-tested elements should be backported. - RC1 beginning of next week - Bug squashing effort during the two weeks that follow. - RC2 around June 15th. - Another week of bug squashing, if necessary. - Release of 6.4.4 by end of June, the latest. That sound ok ? Moritz ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
On Fri, May 16, 2014 at 2:38 PM, Moritz Lennert wrote: > On 15/05/14 23:14, Markus Neteler wrote: ... >>> Draft announcement to be updated: >>> http://trac.osgeo.org/grass/wiki/Release/6.4.4RC1-News >>> >> "Important bugs concerning the next release" >> https://trac.osgeo.org/grass/report/13 Here the full list of issues but none is a blocker: https://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&group=status&milestone=6.4.4 >>> >>> To test on Windows: >>> g.remove cannot remove vector map because of space in DB layer name >>> https://trac.osgeo.org/grass/ticket/1438 > > > You note that this should be wontfix. What do you want to be tested ? Right, nothing to be tested I guess. To be closed? >>> r.univar NaN >>> https://trac.osgeo.org/grass/ticket/2269 >> >> ... missing output to be changed (all GRASS versions). > > > I see this more as an enhancement request than a bug. I don't think this > should hold up a release. ok. >>> - >>> r.walk backport >>> https://trac.osgeo.org/grass/ticket/1628 >> >> ... not sure what to backport. Markus Metz may have an idea. >>> v.kcv backport >>> https://trac.osgeo.org/grass/ticket/2035 >> > See my comment in the ticket. The vector overwrite issue in other mapsets seems to be a general problem, see ticket. >> And/or I can tag RC1 now and we do these issues later. > > I think that except for the r.walk segfault, none are really showstoppers. > And even that only seems to be reproducible in a very specific situation. Given the recent discussion elsewhere I am stuck here. Do you want me to tag RC1 or wait ...? Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
On 15/05/14 23:14, Markus Neteler wrote: On Thu, May 15, 2014 at 12:56 AM, Markus Neteler wrote: On Mon, May 5, 2014 at 8:52 PM, Markus Neteler wrote: On Tue, Apr 29, 2014 at 6:29 PM, Markus Neteler wrote: On Sun, Apr 20, 2014 at 7:38 PM, Markus Neteler wrote: in order to prepare the 6.4.4RC1, please check: Draft announcement to be updated: http://trac.osgeo.org/grass/wiki/Release/6.4.4RC1-News "Important bugs concerning the next release" https://trac.osgeo.org/grass/report/13 Here the full list of issues but none is a blocker: https://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&group=status&milestone=6.4.4 Here some relevant ones: Thanks for having solved some of the issues in the past 24 hours. To test on Windows: g.remove cannot remove vector map because of space in DB layer name https://trac.osgeo.org/grass/ticket/1438 You note that this should be wontfix. What do you want to be tested ? r.univar NaN https://trac.osgeo.org/grass/ticket/2269 ... missing output to be changed (all GRASS versions). I see this more as an enhancement request than a bug. I don't think this should hold up a release. - r.walk backport https://trac.osgeo.org/grass/ticket/1628 ... not sure what to backport. v.kcv backport https://trac.osgeo.org/grass/ticket/2035 ... any objections to submit the patch? See my comment in the ticket. And/or I can tag RC1 now and we do these issues later. I think that except for the r.walk segfault, none are really showstoppers. And even that only seems to be reproducible in a very specific situation. Moritz ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
On Thu, May 15, 2014 at 12:56 AM, Markus Neteler wrote: > On Mon, May 5, 2014 at 8:52 PM, Markus Neteler wrote: >> On Tue, Apr 29, 2014 at 6:29 PM, Markus Neteler wrote: >>> On Sun, Apr 20, 2014 at 7:38 PM, Markus Neteler wrote: in order to prepare the 6.4.4RC1, please check: > > Draft announcement to be updated: > http://trac.osgeo.org/grass/wiki/Release/6.4.4RC1-News > "Important bugs concerning the next release" https://trac.osgeo.org/grass/report/13 >> >> Here the full list of issues but none is a blocker: >> https://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&group=status&milestone=6.4.4 > > Here some relevant ones: Thanks for having solved some of the issues in the past 24 hours. > To test on Windows: > g.remove cannot remove vector map because of space in DB layer name > https://trac.osgeo.org/grass/ticket/1438 ... to be tested. > - > r.univar NaN > https://trac.osgeo.org/grass/ticket/2269 ... missing output to be changed (all GRASS versions). > - > r.walk backport > https://trac.osgeo.org/grass/ticket/1628 ... not sure what to backport. > v.kcv backport > https://trac.osgeo.org/grass/ticket/2035 ... any objections to submit the patch? And/or I can tag RC1 now and we do these issues later. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
On Mon, May 5, 2014 at 8:52 PM, Markus Neteler wrote: > On Tue, Apr 29, 2014 at 6:29 PM, Markus Neteler wrote: >> On Sun, Apr 20, 2014 at 7:38 PM, Markus Neteler wrote: >>> in order to prepare the 6.4.4RC1, please check: Draft announcement to be updated: http://trac.osgeo.org/grass/wiki/Release/6.4.4RC1-News >>> "Important bugs concerning the next release" >>> https://trac.osgeo.org/grass/report/13 > > Here the full list of issues but none is a blocker: > https://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&group=status&milestone=6.4.4 Here some relevant ones: To test on Windows: r.kappa: call to r.stats fails if spaces in path https://trac.osgeo.org/grass/ticket/2116 g.remove cannot remove vector map because of space in DB layer name https://trac.osgeo.org/grass/ticket/1438 - v.external gui exceeds the border of the screen https://trac.osgeo.org/grass/ticket/2159 r.univar NaN https://trac.osgeo.org/grass/ticket/2269 - r.walk backport https://trac.osgeo.org/grass/ticket/1628 v.kcv backport https://trac.osgeo.org/grass/ticket/2035 Perhaps some could be done before tagging RC1? Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
Hi Markus, 2014-05-05 20:52 GMT+02:00 Markus Neteler : > Ready to tag RC1, I would say. one big +1. Martin -- Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
On Tue, Apr 29, 2014 at 6:29 PM, Markus Neteler wrote: > On Sun, Apr 20, 2014 at 7:38 PM, Markus Neteler wrote: >> in order to prepare the 6.4.4RC1, please check: >> >> "Important bugs concerning the next release" >> https://trac.osgeo.org/grass/report/13 Here the full list of issues but none is a blocker: https://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&group=status&milestone=6.4.4 Ready to tag RC1, I would say. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
Hi, 2014-04-29 18:29 GMT+02:00 Markus Neteler : > now v.buffer has been fixed by Markus Metz (using the GEOS library). > > Please test. > >> I have updated to some extent the draft release notes (please add more): >> https://trac.osgeo.org/grass/wiki/Release/6.4.4RC1-News cool, I would say that it's time for RC1... Martin -- Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
Hi, On Sun, Apr 20, 2014 at 7:38 PM, Markus Neteler wrote: > Hi devs, > > in order to prepare the 6.4.4RC1, please check: > > "Important bugs concerning the next release" > https://trac.osgeo.org/grass/report/13 now v.buffer has been fixed by Markus Metz (using the GEOS library). Please test. > I have updated to some extent the draft release notes (please add more): > https://trac.osgeo.org/grass/wiki/Release/6.4.4RC1-News Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
Hi devs, in order to prepare the 6.4.4RC1, please check: "Important bugs concerning the next release" https://trac.osgeo.org/grass/report/13 I have updated to some extent the draft release notes (please add more): https://trac.osgeo.org/grass/wiki/Release/6.4.4RC1-News Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
Hi devs, some time passed, so we should push RC1 out of the door: Please check: "Important bugs concerning the next release" https://trac.osgeo.org/grass/report/13 and please help to complete the draft release notes: https://trac.osgeo.org/grass/wiki/Release/6.4.4RC1-News thanks Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
On Tue, Dec 17, 2013 at 11:02 PM, Michael Barton wrote: ... > Also, there is chatter in the terminal on opening nviz. > > GRASS_INFO_MESSAGE(75334,4): Loading raster map ... > GRASS_INFO_END(75334,4) > > GRASS_INFO_PERCENT: 0 > GRASS_INFO_PERCENT: 3 > GRASS_INFO_PERCENT: 6 > GRASS_INFO_PERCENT: 9 > … There is a similar ticket open: https://trac.osgeo.org/grass/ticket/312 How to catch this GRASS_INFO_PERCENT output? Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
I started compiling GRASS 6.4, release branch last Friday but was only able to test it today. It seems to work fine under Mavericks for Mac. Here are a couple a minor issues I noticed. When I first tried to use nviz (3D display), it failed, with an error message in the console. But it worked fine every time since then, even after restarting GRASS. Also, there is chatter in the terminal on opening nviz. GRASS_INFO_MESSAGE(75334,4): Loading raster map ... GRASS_INFO_END(75334,4) GRASS_INFO_PERCENT: 0 GRASS_INFO_PERCENT: 3 GRASS_INFO_PERCENT: 6 GRASS_INFO_PERCENT: 9 … and GRASS_INFO_MESSAGE(75334,6): Translating colors from raster map ... GRASS_INFO_END(75334,6) GRASS_INFO_PERCENT: 0 GRASS_INFO_PERCENT: 3 GRASS_INFO_PERCENT: 6 GRASS_INFO_PERCENT: 9 Probably a simple fix if you know where to find it. MIchael __ C. Michael Barton Director, Center for Social Dynamics & Complexity Professor of Anthropology, School of Human Evolution & Social Change Arizona State University Tempe, AZ 85287-2402 USA voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC) fax: 480-965-7671(SHESC), 480-727-0709 (CSDC) www: http://csdc.asu.edu, http://shesc.asu.edu http://www.public.asu.edu/~cmbarton On Dec 12, 2013, at 11:32 PM, Michael Barton mailto:michael.bar...@asu.edu>> wrote: At the moment, GRASS 6.5 is not compiling on the Mac under OS X 10.9 (Mavericks). Michaesl C. Michael Barton Director, Center for Social Dynamics & Complexity Professor of Anthropology, School of Human Evolution & Social Change 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<http://csdc.asu.edu/> On Dec 12, 2013, at 11:23 PM, 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] 6.4.4 planning Date: December 12, 2013 at 3:01:22 PM MST To: GRASS developers list mailto:grass-dev@lists.osgeo.org>> On Sun, Nov 24, 2013 at 4:32 PM, Helmut Kudrnovsky mailto:hel...@web.de>> wrote: Markus Neteler wrote On Sat, Nov 16, 2013 at 3:00 AM, Hamish on the grass-user ML Markus N wrote: (and it is time to get 6.4.4 out...) "Important bugs concerning the next release" https://trac.osgeo.org/grass/report/13 ... see http://trac.osgeo.org/grass/ticket/2138 for the actual state of python addons in winGRASS6.5.svn/6.4.svn. we are near to working python addon scripts in winGRASS :-) this seem to be the one and only thing blocking 6.4.4RC1... Any suggestions to get it done? Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
On Fri, Dec 13, 2013 at 2:52 AM, Markus Neteler wrote: > Hi Anna, > > On Fri, Dec 13, 2013 at 1:19 AM, Anna Petrášová > wrote: > > Hi, > > > > I almost forgot about a patch for nviz which is now in GRASS 7 since > August > > [1]. It should be probably backported. I have been testing isosurfaces > quite > > a lot with different data and I have almost no crashes now. But I test > only > > on Linux. The reason for this patch is in this ticket [2]. > > So if you don't have any objection I will backport it. > > Please do - as we know things only get tested when easily usable. And > at time we are planning for RC1 and not the final release. > thanks > Markus > done in r58481, r58482 Anna > > Anna > > > > > > [1] http://trac.osgeo.org/grass/changeset/57620 > > [2] http://trac.osgeo.org/grass/ticket/1736#comment:26 > > > > > ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
Hi Anna, On Fri, Dec 13, 2013 at 1:19 AM, Anna Petrášová wrote: > Hi, > > I almost forgot about a patch for nviz which is now in GRASS 7 since August > [1]. It should be probably backported. I have been testing isosurfaces quite > a lot with different data and I have almost no crashes now. But I test only > on Linux. The reason for this patch is in this ticket [2]. > So if you don't have any objection I will backport it. Please do - as we know things only get tested when easily usable. And at time we are planning for RC1 and not the final release. thanks Markus > Anna > > > [1] http://trac.osgeo.org/grass/changeset/57620 > [2] http://trac.osgeo.org/grass/ticket/1736#comment:26 > > ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
At the moment, GRASS 6.5 is not compiling on the Mac under OS X 10.9 (Mavericks). Michaesl C. Michael Barton Director, Center for Social Dynamics & Complexity Professor of Anthropology, School of Human Evolution & Social Change 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 Dec 12, 2013, at 11:23 PM, 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] 6.4.4 planning Date: December 12, 2013 at 3:01:22 PM MST To: GRASS developers list mailto:grass-dev@lists.osgeo.org>> On Sun, Nov 24, 2013 at 4:32 PM, Helmut Kudrnovsky mailto:hel...@web.de>> wrote: Markus Neteler wrote On Sat, Nov 16, 2013 at 3:00 AM, Hamish on the grass-user ML Markus N wrote: (and it is time to get 6.4.4 out...) "Important bugs concerning the next release" https://trac.osgeo.org/grass/report/13 ... see http://trac.osgeo.org/grass/ticket/2138 for the actual state of python addons in winGRASS6.5.svn/6.4.svn. we are near to working python addon scripts in winGRASS :-) this seem to be the one and only thing blocking 6.4.4RC1... Any suggestions to get it done? Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
Hi, I almost forgot about a patch for nviz which is now in GRASS 7 since August [1]. It should be probably backported. I have been testing isosurfaces quite a lot with different data and I have almost no crashes now. But I test only on Linux. The reason for this patch is in this ticket [2]. So if you don't have any objection I will backport it. Anna [1] http://trac.osgeo.org/grass/changeset/57620 [2] http://trac.osgeo.org/grass/ticket/1736#comment:26 On Thu, Dec 12, 2013 at 5:01 PM, Markus Neteler wrote: > On Sun, Nov 24, 2013 at 4:32 PM, Helmut Kudrnovsky wrote: > > Markus Neteler wrote > >> On Sat, Nov 16, 2013 at 3:00 AM, Hamish > >>> on the grass-user ML Markus N wrote: > (and it is time to get 6.4.4 out...) > >>> > >>> "Important bugs concerning the next release" > >>> https://trac.osgeo.org/grass/report/13 > ... > > > see http://trac.osgeo.org/grass/ticket/2138 for the actual state of > python > > addons in winGRASS6.5.svn/6.4.svn. > > > > we are near to working python addon scripts in winGRASS :-) > > this seem to be the one and only thing blocking 6.4.4RC1... > Any suggestions to get it done? > > Markus > ___ > 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] 6.4.4 planning
On Sun, Nov 24, 2013 at 4:32 PM, Helmut Kudrnovsky wrote: > Markus Neteler wrote >> On Sat, Nov 16, 2013 at 3:00 AM, Hamish >>> on the grass-user ML Markus N wrote: (and it is time to get 6.4.4 out...) >>> >>> "Important bugs concerning the next release" >>> https://trac.osgeo.org/grass/report/13 ... > see http://trac.osgeo.org/grass/ticket/2138 for the actual state of python > addons in winGRASS6.5.svn/6.4.svn. > > we are near to working python addon scripts in winGRASS :-) this seem to be the one and only thing blocking 6.4.4RC1... Any suggestions to get it done? Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
Markus Neteler wrote > On Sat, Nov 16, 2013 at 3:00 AM, Hamish < > hamish_b@ > > wrote: >> on the grass-user ML Markus N wrote: >>> (and it is time to get 6.4.4 out...) >> >> "Important bugs concerning the next release" >> https://trac.osgeo.org/grass/report/13 > > No blocker at time! > >> The other two important tasks for 6.4.4 in my mind are to get python >> addon >> scripts working with 6.4's g.extension.py, both for Linux and WinGrass >> (#1768, >> just committed an experimental change to 6.5svn a few days ago; e.g. for >> r.threshold), > > Yes, that's indeed important. > (reference: https://trac.osgeo.org/grass/changeset/58199 ) see http://trac.osgeo.org/grass/ticket/2138 for the actual state of python addons in winGRASS6.5.svn/6.4.svn. we are near to working python addon scripts in winGRASS :-) - best regards Helmut -- View this message in context: http://osgeo-org.1560.x6.nabble.com/6-4-4-planning-tp5089457p5090880.html Sent from the Grass - Dev mailing list archive at Nabble.com. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
On Sat, Nov 16, 2013 at 3:00 AM, Hamish wrote: > on the grass-user ML Markus N wrote: >> (and it is time to get 6.4.4 out...) > > > fwiw, > > I've gone through the two branches with kdiff3 and selectively backported > many of the differences between the branches. There are a number of > experiments and minor cosmetic changes which I didn't backport. One big > remaining hope I had for 6.4.4 was to backport the parallelization work > in the imagery scripts, e.g. i.landsat.rgb. I think they are pretty good > but I haven't tried them on WinGrass to learn how well MSys deals with > backgrounding jobs with "&". I had planned to merge scripts/ first, to > give them the maximum amount of testing in the stable branch, but it turned > out to be too big a job for the small windows of time I could give to it. > But now I am mostly waiting on testing them in 6.5 nightly WinGrass. I think that this parallelization work should wait for 6.4.5 or whatever (also given your available time). Draft release notes: https://trac.osgeo.org/grass/wiki/Release/6.4.4RC1-News --> 14 tickets closed which is already nice. > > "Important bugs concerning the next release" > https://trac.osgeo.org/grass/report/13 No blocker at time! > The other two important tasks for 6.4.4 in my mind are to get python addon > scripts working with 6.4's g.extension.py, both for Linux and WinGrass (#1768, > just committed an experimental change to 6.5svn a few days ago; e.g. for > r.threshold), Yes, that's indeed important. (reference: https://trac.osgeo.org/grass/changeset/58199 ) > and secondly to get the Cairo driver working on WinGrass (#943). > > The Cairo driver seems to need some G_spawn() pipe handling/closing in d.mon, > using SF_BACKGROUND and other popen flags which I just stumble around in the > dark with & need some assistance. Maybe Glynn knows? Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
