[GRASS-dev] Re: grass cvs2svn migration status

[Glynn Clements]

Martin Landa wrote:

> Hi all,
> 
> let me inform you about progress in cvs2svn migration.
> 
> There are three different SVN repo proposals, see [1]. After
> discussion with several people (thanks also to Markus), the best
> solution seems to be [2]. The scripts used for the conversion and log
> files (including properties test) are available on-line [3], the
> *testing SVN repo* [4]:
> 
> http://josef.fsv.cvut.cz/cgi-bin/viewcvs.cgi/?root=grass-svn2
> 
> There is still one problem, on the history page [5] are mentioned few
> releases which I cannot find in CVS (or migrated SVN) repo:
> 
> # 8/2005 GRASS 6.0.1RC1 version from ITC-irst/GRASS Development Team
> # 8/2005 GRASS 6.0.1RC2 version from ITC-irst/GRASS Development Team
> # 22 Aug. 2005 GRASS 6.0.1 version from ITC-irst/GRASS Development Team
> # 29 Dec. 2005 GRASS 6.0.2RC1 version from ITC-irst/GRASS Development Team
> # 3 Jan. 2006 GRASS 6.0.2RC2 version from ITC-irst/GRASS Development Team
> # 3 Jan. 2006 GRASS 6.0.2RC3 version from ITC-irst/GRASS Development Team
> # 6 Jan. 2006 GRASS 6.0.2RC4 version from ITC-irst/GRASS Development Team

They don't appear to have been tagged; someone just tarred up the
current state of the releasebranch_6_0 branch and called it a release.

The following log entries for the VERSION file indicate the dates:

    $ cvs log include/VERSION 
    
    RCS file: /grassrepository/grass6/include/VERSION,v
    Working file: include/VERSION
    head: 1.17
    branch:
    locks: strict
    access list:
    symbolic names:
    	release_20071120_grass_6_3_0RC2: 1.17.2.3
    	release_20071024_grass_6_3_0RC1: 1.17.2.1
    	releasebranch_6_3: 1.17.0.2
    	release_20071021_grass_6_2_3RC1: 1.15.4.30
    	release_20070716_grass_6_2_2: 1.15.4.28
    	grass_6_2_2RC1: 1.15.4.26
    	grass_6_2_1: 1.15.4.18
    	grass_6_2_1RC1: 1.15.4.16
    	grass_6_2_0: 1.15.4.14
    	grass_6_2_0RC3: 1.15.4.12
    	grass_6_2_0RC2: 1.15.4.10
    	grass_6_2_0RC1: 1.15.4.8
    	grass_6_2_0beta3: 1.15.4.6
    	grass_6_2_0beta2: 1.15.4.4
    	grass_6_2_0beta1: 1.15.4.2
    	releasebranch_6_2: 1.15.0.4
    	grass_6_1_0: 1.15.2.4
    	grass_6_1_0RC1: 1.15.2.2
    	grass_6_1_0beta1: 1.15.2.1
    	grass_6_0_0beta1: 1.15.2.1
    	releasebranch_6_1: 1.15.0.2
    	grass_6_0_2: 1.13.2.21
    	grass_6_0_0: 1.13.2.1
    	releasebranch_6_0: 1.13.0.2
    	grass_6_0_0_beta_2: 1.12
    	grass_6_0_0_beta_1: 1.10
    	release_17_06_2004_grass5_7_0: 1.6
    keyword substitution: kv
    total revisions: 80;	selected revisions: 80
    description:
    ----------------------------
    revision 1.13.2.17
    date: 2006/01/06 22:40:50;  author: markus;  state: Exp;  lines: +1 -1
    GRASS 6.0.2RC4
    ----------------------------
    revision 1.13.2.14
    date: 2006/01/03 12:58:49;  author: markus;  state: Exp;  lines: +1 -1
    6.0.2RC3
    ----------------------------
    revision 1.13.2.12
    date: 2006/01/03 10:36:24;  author: markus;  state: Exp;  lines: +1 -1
    GRASS 6.0.2RC2
    ----------------------------
    revision 1.13.2.10
    date: 2005/12/29 22:37:03;  author: markus;  state: Exp;  lines: +1 -1
    6.0.2RC1
    ----------------------------
    revision 1.13.2.7
    date: 2005/08/22 08:17:15;  author: markus;  state: Exp;  lines: +1 -1
    6.0.1 release
    ----------------------------
    revision 1.13.2.5
    date: 2005/08/08 20:43:46;  author: markus;  state: Exp;  lines: +1 -1
    RC2 - relase canditate 2
    ----------------------------
    revision 1.13.2.3
    date: 2005/08/03 15:51:07;  author: markus;  state: Exp;  lines: +1 -1
    6.0.1RC1

If you want to tag the above releases, you can try updating to the
corresponding date with "cvs update -D ..." and compare the local copy
against the tarballs at:

	http://grass.itc.it/grass60/source/

If the files all match, you can then tag the repository.

In an ideal world, the tarballs would include the CVS directories, but
I don't think that's the case for GRASS releases.

-- 
Glynn Clements <glynn at gclements.plus.com>