[GRASS-dev] too many branches

Michael Barton Michael.Barton at asu.edu
Sat Aug 25 08:42:10 PDT 2012

My suggestion was to start a GRASS 7 release branch and stop adding new features to 6.x *after* 6.4.4 stable is released. Too complicated to work on 2 active release branches at the same time.

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-727-9746 (CSDC)
fax:          480-965-7671 (SHESC),  480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu

On Aug 25, 2012, at 8:09 AM, <grass-dev-request at lists.osgeo.org<mailto:grass-dev-request at lists.osgeo.org>>

From: Helena Mitasova <hmitaso at ncsu.edu<mailto:hmitaso at ncsu.edu>>
Subject: Re: [GRASS-dev] too many branches
Date: August 24, 2012 3:22:00 PM MST
To: Martin Landa <landa.martin at gmail.com<mailto:landa.martin at gmail.com>>
Cc: GRASS developers list <grass-dev at lists.osgeo.org<mailto:grass-dev at lists.osgeo.org>>


I agree.
I think we have too many issues with 6.4* that need to be resolved quickly that we can start thinking about grass7
after we have a stable (in the sense as described by Glynn)
version of GRASS  that people can download and that works.

Currently, we have stable GRASS6.4.2, but it is not very useable on Windows
and GRASS6.4.3 changes every day so students have different versions depending on when they downloaded
and addressing any issues that they may have gets messy pretty quickly.
Moreover, there are issues with Mac binaries as well.


On Aug 24, 2012, at 8:37 AM, Martin Landa wrote:


2012/8/22 Markus Neteler <neteler at osgeo.org<mailto:neteler at osgeo.org>>:
PS: As a user I can not use 6.x for production work because GRASS 6 is
not able to perform the kind of analyses I have to do for my job. I
have to use GRASS 7.

... so the idea to start a GRASS 7 release branch would address that nicely.

we started discussion with an idea to reduce number of branches we
currently maintain ;-) I personally think it's too much soon for grass
7 release branch. Let's say I would postpone it to the beginning of
the next year, then GRASS 7 could be released eg. around June. Make
sense to you?


Martin Landa <landa.martin gmail.com<http://gmail.com/>> * http://geo.fsv.cvut.cz/~landa
grass-dev mailing list
grass-dev at lists.osgeo.org<mailto:grass-dev at lists.osgeo.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20120825/361acbe7/attachment.html>

More information about the grass-dev mailing list