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

Helena Mitasova hmitaso at ncsu.edu
Mon Jun 13 22:30:18 EDT 2011

On Jun 13, 2011, at 4:17 PM, Hamish wrote:

> Martin wrote:
>> done in r46687 (review needed).
> n.b. r46690 code still refers to .grass7 in grass6
> [please don't backport to 6.4 until code is tested in 6.5 for some
> time, even if it seems harmless. otherwise there is no quality
> control, the laws of unintended consequences bite us, and what's
> the point of maintaining a 6.5 testing branch at all? tx]

just a note regarding your testing comment
- we discussed the need for testing before backporting to 6.4 with Martin,
so the main issue is to stick with it and make sure it happens.
Hopefully we don't need any official procedure for guarding the stability of 
what should be a stable release,

> addon environ variable can have multiples, you need to spit on
> the first ":".
> the shell script version in 6.x already installs to the addon dir
> as part of g.extension.sh, with sudo,su options to go to the
> install dir upon request. should we stay with that and/or is a specific install target needed? (why is a python clone needed
> there? to help with menu integration? is there a bug in wingrass
> I don't know about?)
> Hamish
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev

More information about the grass-dev mailing list