[GRASS-user] SVN Branches

GRASS GRASS user
1

   If there is a stable -6.4 release that's updated weekly, why is there also
a -6.4 release candidate 5 branch? My understanding is that release
candidates precede releases and are mooted once the version has been
released.

Confused,

Rich

2

On Wed, Feb 17, 2010 at 3:34 PM, Rich Shepard <rshepard@appl-ecosys.com> wrote:

If there is a stable -6.4 release that's updated weekly, why is there also
a -6.4 release candidate 5 branch? My understanding is that release
candidates precede releases and are mooted once the version has been
released.

Please indicate the URLs to better understand the confusion.

We have
- 6.4.release-branch from which RC5 was extracted some months ago
  -> weekly source code and Linux binary snapshots are generated
  -> daily winGRASS binaries are generated

- 6.5.devel-branch
  -> weekly source code and Linux binary snapshots are generated
  -> daily winGRASS binaries are generated

- 7.trunk
  -> weekly source code and Linux binary snapshots are generated
  -> daily winGRASS binaries are generated

If you indicate the suboptimal web page(s), we may be able to
clarify things there, too.

Markus

3

On Wed, 17 Feb 2010, Markus Neteler wrote:

We have
- 6.4.release-branch from which RC5 was extracted some months ago
-> weekly source code and Linux binary snapshots are generated
-> daily winGRASS binaries are generated

Markus,

   Do I interpret the above that you extracted RC5 from the stable release?

   Here's the URL: <http://trac.osgeo.org/grass/wiki/DownloadSource#GRASS6.4&gt;
and this is what I see:

GRASS 6.4

To extract the current 6.4.0 release candidate 5 (RC5) use the command:

   svn checkout https://svn.osgeo.org/grass/grass/tags/release_20090609_grass_6_4_0RC5 grass640_rc5

To extract the current 6.4.x release branch version (stable) use the command:

   svn checkout https://svn.osgeo.org/grass/grass/branches/releasebranch_6_4 grass64_release

   Are you developing both the stable and release candidate versions
simultaneously? Do both have identical code? If I want the patch you added
late last week which branch do I use?

Thanks,

Rich

4

On Wed, Feb 17, 2010 at 4:55 PM, Rich Shepard <rshepard@appl-ecosys.com> wrote:

On Wed, 17 Feb 2010, Markus Neteler wrote:

We have
- 6.4.release-branch from which RC5 was extracted some months ago
-> weekly source code and Linux binary snapshots are generated
-> daily winGRASS binaries are generated

Markus,

Do I interpret the above that you extracted RC5 from the stable release?

Here's the URL: <http://trac.osgeo.org/grass/wiki/DownloadSource#GRASS6.4&gt;
and this is what I see:

GRASS 6.4

To extract the current 6.4.0 release candidate 5 (RC5) use the command:

svn checkout
https://svn.osgeo.org/grass/grass/tags/release_20090609_grass_6_4_0RC5
grass640_rc5

To extract the current 6.4.x release branch version (stable) use the
command:

svn checkout https://svn.osgeo.org/grass/grass/branches/releasebranch_6_4
grass64_release

Now I understand your confusion.

I have inverted the order and changed the wording to

GRASS 6.4
To extract the current state of the 6.4.x release branch version
(stable), use the command:
  svn checkout https://svn.osgeo.org/grass/grass/branches/releasebranch_6_4
grass64_release

To extract the 6.4.0 release candidate 5 (RC5) from 2009, use the command:
  svn checkout https://svn.osgeo.org/grass/grass/tags/release_20090609_grass_6_4_0RC5
grass640_rc5

Does it make more sense now?

Are you developing both the stable and release candidate versions
simultaneously? Do both have identical code? If I want the patch you added
late last week which branch do I use?

then use "the current state of the 6.4.x release branch" (so the upper after the
modification).

You can simply stay on that branch and update with
svn up
from time to time to fetch latest fixes. I am using that for my production
systems.

Markus

5

On Wed, 17 Feb 2010, Markus Neteler wrote:

Now I understand your confusion.

   Whew! :slight_smile:

I have inverted the order and changed the wording to

GRASS 6.4
To extract the current state of the 6.4.x release branch version
(stable), use the command:
svn checkout https://svn.osgeo.org/grass/grass/branches/releasebranch_6_4
grass64_release

To extract the 6.4.0 release candidate 5 (RC5) from 2009, use the command:
svn checkout https://svn.osgeo.org/grass/grass/tags/release_20090609_grass_6_4_0RC5
grass640_rc5

Does it make more sense now?

   It certainly does, Markus.

then use "the current state of the 6.4.x release branch" (so the upper
after the modification).

   That's what I thought and what I've been doing.

Many thanks,

Rich