Hamish wrote: > > Grass64-Release => %ProgramFiles%\GRASS-64 > > Grass64-Dev => %ProgramFiles%\GRASS-64-SVN > ... > > We *need* this to work. If GRASS can't handle being > > installed in %ProgramFiles%, that's a blocker, IMHO. > > > It could be that this is a 6.4.0-final blocker, but //please// let's > hold off on r40496 and release 6.4.0rc6 before beginning to validate > that $GISBASE is space-safe.
If not now, then when? We need at least one RC which installs into %ProgramFiles% by default. If that isn't RC6, then we will need an RC7 even if RC6 appears to work perfectly, and if it turns out that there *are* problems with RC7, then we would need an RC8 to test the fixes. > AFAIK there are no more major RC-blockers left & we are ready to go > for rc6 -right now-. Fine. Then release RC6 -right now-, with the default installation directory as %ProgramFiles%\GRASS-64-RC6. > If we start on the next thing it's going to be > another 3 weeks+ before we can even think about shipping rc6. !...@$%!# > It resets the release confidence cycle. At the risk of stating the obvious, a "release candidate" (as opposed to a "beta") is ... a candidate for release. If no bugs are found, then the RC gets released as the "release", with the only change being that it's called "6.4.0" rather than "6.4.0-RC<something>". If you know for a fact that the "RC" won't actually become the release, even if no (significant) bugs are found, then it *isn't* a "release candidate". -- Glynn Clements <[email protected]> _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
