CVS2SVN

["Adam R. B. Jack" <aj...@apache.org>]

Stefano and Justin have performed the copy from CVS to SVN, with
all CVS history, so it is time to tag both SCM repositories as
CVS2SVN (I also did 'TRADITIONAL') and:

1) Strip CVS to be metadata only
2) Strip SVN (to remove TRADITIONAL, i.e non-Python).
3) RE-org SVN (to make sense for Python Gump)

As part of this I see the following need:

1) Convert Peas-and-Carrots (./blog) to use SVN (or keep it as CVS). Nick?
2) Convert gumpy.py to:
    1) Check [and Update] Gump code out of SVN
    2) Check [and Update] Gump metadata from CVS into ./metadata

The reason for the ./metadata sub-directory is both for organization
and so SVN and CVS don't have opportunity to clash.

3) Create the SVN properties (c.f. .cvsignore).
4) Wipe brutus' ./{flavour}/gump CVS directories, and re-checkout
5) Update the 'getting started' pages, including on gump.apache.org


Any other thoughts on work for this step?

regards

Adam
--
Have you Gump'ed your code today?
http://gump.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org

Re: CVS2SVN

[Nick Chalko <ni...@chalko.com>]

Adam R. B. Jack wrote:

> Stefano and Justin have performed the copy from CVS to SVN, with
> all CVS history, so it is time to tag both SCM repositories as
> CVS2SVN (I also did 'TRADITIONAL') and:
>
> 1) Strip CVS to be metadata only
> 2) Strip SVN (to remove TRADITIONAL, i.e non-Python).
> 3) RE-org SVN (to make sense for Python Gump)
>
> As part of this I see the following need:
>
> 1) Convert Peas-and-Carrots (./blog) to use SVN (or keep it as CVS). 
> Nick?

That is fine with me.
\