[GRASS-dev] Re: testing in 6.5 before backporting to 6.4

Michael Barton Michael.Barton at asu.edu
Fri Jun 17 16:29:53 EDT 2011

No disagreement from me on this.

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

voice: 	480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax:          480-965-7671(SHESC), 480-727-0709 (CSDC)
www: 	http://csdc.asu.edu, http://shesc.asu.edu

On Jun 17, 2011, at 1:27 PM, Martin Landa wrote:

> Hi all,
> 2011/6/17 Michael Barton <michael.barton at asu.edu>:
>> The lack of manpower makes it even more important that all developers test any changes before committing--including backporting.
> I guess there is no one who is against testing. The subjective point
> of view is "how much" the committed changes are tested. It depends on
> the contributor, what he/she is committing (core libs, modules, GUI),
> release life cycle (speaking about stable releases), etc. There is no
> measurement, I believe everyone is going her/his best. Even someone
> can have different impression. The important issue is to have working
> test suites (modules - thanks Soeren for good work, GUI, etc).
> Martin
> -- 
> Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa

More information about the grass-dev mailing list