I have been using [1] as the version of GRASS that I use on a regular basis. I
see that this version refers to itself as GRASS-7, and uses a new install
target (as opposed to 'grass-6.3.svn').
Would it be wise to track the 'releasebranch_6_3' for a more stable GRASS
experience? Does this version contain everything that 'trunk' had in it as of
about a month ago?
All of this started when I was stuck by the bug associated with [2] .
As of now I was thinking about keeping one source dir in sync with 6.3 and one
with trunk, so that I have a stable environment, but can still try out the
new features in 7.0 .
I have been using [1] as the version of GRASS that I use on
a regular basis. I see that this version refers to itself as
GRASS-7, and uses a new install target (as opposed to
'grass-6.3.svn').
Would it be wise to track the 'releasebranch_6_3' for a more stable
GRASS experience? Does this version contain everything that
'trunk' had in it as of about a month ago?
no it is in bug fix only mode. even then 6.3.1 may or may not happen.
grass7 is likely to become unusable for a time.
All of this started when I was stuck by the bug associated with [2] .
As of now I was thinking about keeping one source dir in
sync with 6.3 and one with trunk, so that I have a stable
environment, but can still try out the new features in 7.0 .
Any tips?
yeah, use 'develbranch_6' instead of trunk or 'releasebranch_6_3'.