Xalan migration from CVS to Subversion 2005-10-27 - By Brian Minchau
The Xalan committers have voted to move from CVS to Subversion as the code
repository.
This will most likely happen early to mid next week (Nov. 1 or 2). There
is a Subversion test repository that should look like the code when
migrated (thanks to Henri Yandell). Please have a look (especially Xalan
committers) and post to xalan-dev@(protected) if you have concerns, or
even if it looks OK.
Thanks,
- Brian
- - - - - - - - - - - - - - - - - - - -
Brian Minchau
Apache Xalan PMC
----- Forwarded by Brian Minchau/Toronto/IBM on 10/27/2005 12:08 PM -----
Henri Yandell
<bayard@(protected)
g> To
Brian Minchau/Toronto/IBM@(protected)
10/11/2005 11:50 cc
PM
Subject
Re: Xalan migration...
Okay, here you go, test migration:
http://svn.apache.org/repos/test/xalan/
svn co https://svn.apache.org/repos/test/xalan/java/trunk xalan-java
svn co https://svn.apache.org/repos/test/xalan/c/trunk xalan-c
svn co https://svn.apache.org/repos/test/xalan/test/trunk xalan-test
Should give you something to look at. I had to add the following flags:
cvs2svn --dump-only --dumpfile=java.dump --force-branch=XSLTC_DOMImpl
xml-xalan/java
cvs2svn --dump-only --dumpfile=c.dump --force-branch=LotusXSL4C_1_3_0-390
--force-branch=LotusXSL4C_1_3_0 --force-branch=LotusXSL4C_1_0_0
--force-branch=LotusXSL4C_1_3_1 xml-xalan/c
cvs2svn --dump-only --dumpfile=test.dump --encoding=latin1 xml-xalan/test
The --force-branches are because CVS gets a bit confused sometimes and
you end up with a tag-name which is a tag in N files and a branch in a
few; or a branch in N files and a tag in a few. The xalan-c ones were tags
which had been modified a few times, so I went ahead and let them become
branches. The xalan-java one was a branch that had never been edited and
was a tag in a few files, so I let it stay a branch. Safest course of
action.
The --encoding is because xalan-test has some odd characters in the
filenames. So checking any obscure filenames you have would be a very good
thing to do; it should stay the same provided they fit within latin1.
If there are problems, I think we can do other encoding things, I've just
not had to yet.
Let me know how it all looks,
Hen
On Tue, 11 Oct 2005, Brian Minchau wrote:
> Henri,
> the Xalan committers just voted to move to SVN last week. We are waiting
> for a Xalan-C release 1.10, which should come out within the week. After
> that we will move to SVN.
>
> I'll have a closer look at what you did. At first glance it seems to be
> very close to what the team has agreed to.
>
> Here is what the Xalan committers think should be migrated:
>
===============================================================================
==========
>
> In the existing structure under xml-xalan in CVS, the following are dead,
> and will not be migrated:
> * xml-xalan/bin
> * xml-xalan/docs
> * xml-xalan/samples
> * xml-xalan/src
> * xml-xalan/xdocs
>
> In the existing structure under xml-xalan in CVS, the following be
> migrated:
> * xml-xalan/c
> * xml-xalan/java
> * xml-xalan/test
>
> https://svn.apache.org/repos/asf/xalan
>
>
>
> Under this I propose these "directories"
> * /java/branches (Xalan-j branches)
> * /java/tags (Xalan-j tags)
> * /java/trunk (Xalan-j HEAD)
>
> * /c/branches (Xalan-C branches)
> * /c/tags (Xalan-C tags)
> * /c/trunk (Xalan-C HEAD)
>
>
> * /test/branches (Xalan branches)
> * /test/tags (Xalan tags)
> * /test/trunk (Xalan HEAD)
>
>
> - Brian
> - - - - - - - - - - - - - - - - - - - -
> Brian Minchau
> Apache Xalan PMC Chairperson
>
>
>
>
>
> Henri Yandell
> <bayard@(protected)
> g> To
> pmc@(protected),
> 10/10/2005 01:57 minchau@(protected)
> PM cc
>
> Subject
> Xalan migration...
>
>
>
>
>
>
>
>
>
>
>
> I went ahead and did a standard-style cvs->svn test migration for
> xml-xalan. No idea if it's what you want, but there's a good chance it
is:
>
> http://svn.apache.org/repos/test/xalan
>
> svn co https://svn.apache.org/repos/test/xalan/trunk xml-xalan
>
> Assuming that a branches/tags/trunk strategy is what you'd like, how does
> that look?
>
> Hen
>
>
|
|
