Re: [GRASS-PSC] too many branches = retirement GRASS6.5.svn (=develbranch6)

2014-04-06 Thread Martin Landa
Hi Markus, 2014-04-06 10:01 GMT+02:00 Markus Metz markus.metz.gisw...@gmail.com: big strong +1 for me, Martin +1 from me too, with one comment: I will only backport bugfixes to a releasebranch, not new functionality. That includes releasebranch_7_0. The (my) objective is to stabilize any

Re: [GRASS-PSC] too many branches = retirement GRASS6.5.svn (=develbranch6)

2014-04-06 Thread Martin Landa
Dear PSC members, 2014-04-06 10:08 GMT+02:00 Martin Landa landa.mar...@gmail.com: +1 from me too, with one comment: I will only backport bugfixes to a releasebranch, not new functionality. That includes releasebranch_7_0. The (my) objective is to stabilize any releasebranch. this should

Re: [GRASS-PSC] too many branches = retirement GRASS6.5.svn (=develbranch6)

2014-04-06 Thread Markus Neteler
On Mon, Mar 31, 2014 at 10:04 AM, Martin Landa landa.mar...@gmail.com wrote: Hi all, 2014-03-31 9:57 GMT+02:00 Sören Gebbert soerengebb...@googlemail.com: +1 I agree to 100% big strong +1 for me, Martin also from me: retire GRASS6.5.svn (=develbranch6). markusN

Re: [GRASS-PSC] too many branches = retirement GRASS6.5.svn (=develbranch6)

2014-04-06 Thread Moritz Lennert
On 06/04/14 13:46, Hamish wrote: First of all, I believe this discussion belongs on the grass-dev list, not PSC. See RFC1. CC'in to dev-list releasebranch70 should not have been branched until 7.0RC1. Until RC1 it is just wasted effort to keep the two of them as a 1:1 mirror, so what's

Re: [GRASS-PSC] too many branches = retirement GRASS6.5.svn (=develbranch6)

2014-04-06 Thread Martin Landa
Hi, 2014-04-06 15:16 GMT+02:00 Moritz Lennert mlenn...@club.worldonline.be: As already mentioned I was also a bit surprised by this. I'm not sure we are really ready for something more than a tech-preview (and not a real release), but maybe it could be the kick in the behind that we need to

Re: [GRASS-PSC] too many branches = retirement GRASS6.5.svn (=develbranch6)

2014-04-06 Thread Markus Metz
On Sun, Apr 6, 2014 at 3:16 PM, Moritz Lennert mlenn...@club.worldonline.be wrote: On 06/04/14 13:46, Hamish wrote: As mentioned before, I wish to use the bulk of my grass dev time maintaining the grass 6 line. To do that properly I need a staging area, and devbr6 is it. I don't see the

Re: [GRASS-PSC] too many branches

2014-03-31 Thread Moritz Lennert
On 29/03/14 07:04, Luca Delucchi wrote: Hi PSC, with the upcoming GRASS 7 release we have to many branches to maintain (releasebranch6, devbranch6, releasebranch7 and trunk). Can I ask you to take a decision about the future of all this branches? I could suggest something like: - keep

Re: [GRASS-PSC] too many branches

2014-03-31 Thread Martin Landa
Dear PSC, 2014-03-31 4:30 GMT+02:00 Yann Chemin yche...@gmail.com: +1 to remove devbranch6 after appropriate transfer of the needed to releasebranch6. same here +1, maybe not to remove, just to set as read only Do we have a tentative time line to freeze Grass6 release branch (1 year?) You

Re: [GRASS-PSC] too many branches

2014-03-31 Thread Markus Neteler
On Mon, Mar 31, 2014 at 4:30 AM, Yann Chemin yche...@gmail.com wrote: In favour of giving the devbranch6 a prune, I cannot remember when I used grass6-dev last time... Obviously will maintain GRASS 6.4.x for more time, that's our LTS... +1 to remove devbranch6 after appropriate transfer of

Re: [GRASS-PSC] too many branches

2014-03-31 Thread Markus Neteler
On Mon, Mar 31, 2014 at 10:24 AM, Moritz Lennert mlenn...@club.worldonline.be wrote: The initial idea was to create a tech-preview release of grass7, not an official 7.0 release. Has that changed during the sprint ? No, this is what happened: beta1 (called like this to maintain consistency with

Re: [GRASS-PSC] too many branches

2014-03-31 Thread Moritz Lennert
On 31/03/14 10:34, Markus Neteler wrote: On Mon, Mar 31, 2014 at 10:24 AM, Moritz Lennert mlenn...@club.worldonline.be wrote: The initial idea was to create a tech-preview release of grass7, not an official 7.0 release. Has that changed during the sprint ? No, this is what happened: beta1

Re: [GRASS-PSC] too many branches

2014-03-30 Thread Scott Mitchell
Along the same lines, I don’t feel in the loop enough to judge specifics, but like the thrust of the discussion. So +0 from me too, if it’s needed. On Mar 30, 2014, at 17:32 , Massimiliano Cannata massimiliano.cann...@supsi.ch wrote: I'm in general in favor, but would like to know the

Re: [GRASS-PSC] too many branches

2014-03-30 Thread Yann Chemin
In favour of giving the devbranch6 a prune, I cannot remember when I used grass6-dev last time... +1 to remove devbranch6 after appropriate transfer of the needed to releasebranch6. Do we have a tentative time line to freeze Grass6 release branch (1 year?) Yann On 29 March 2014 11:34, Luca

Re: [GRASS-PSC] too many branches = retirement GRASS6.5.svn (=develbranch6)

2014-03-30 Thread Yann Chemin
+1 On 30 March 2014 02:47, Helmut Kudrnovsky hel...@web.de wrote: Dear GRASS GIS PSC, margherita wrote Dear Luca, thank you for raising this issue, On Sat, Mar 29, 2014 at 7:04 AM, Luca Delucchi lt; lucadeluge@ gt; wrote: with the upcoming GRASS 7 release we have to

Re: [GRASS-PSC] too many branches

2014-03-29 Thread Margherita Di Leo
Dear Luca, thank you for raising this issue, On Sat, Mar 29, 2014 at 7:04 AM, Luca Delucchi lucadel...@gmail.com wrote: with the upcoming GRASS 7 release we have to many branches to maintain (releasebranch6, devbranch6, releasebranch7 and trunk). Can I ask you to take a decision about the

Re: [GRASS-PSC] too many branches = retirement GRASS6.5.svn (=develbranch6)

2014-03-29 Thread Helmut Kudrnovsky
Dear GRASS GIS PSC, margherita wrote Dear Luca, thank you for raising this issue, On Sat, Mar 29, 2014 at 7:04 AM, Luca Delucchi lt; lucadeluge@ gt; wrote: with the upcoming GRASS 7 release we have to many branches to maintain (releasebranch6, devbranch6, releasebranch7 and