Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 211341

Summary:	Requesting Subversion Repository
Product:	Community	Reporter:	Terran Gilman <trip>
Component:	Subversion	Assignee:	Eclipse Webmaster <webmaster>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	bjorn.freeman-benson, jkobal, lonnie, mike, nobody, tyler
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Terran Gilman

2007-11-28 17:08:45 EST

Hello,

   I'd like to request a new Subversion repository for the Voice Tools Project.  The project currently uses CVS for version control and the developers and I have decided to convert to Subversion.  Thank You.

Trip Gilman
Voice Tools Project Lead

Comment 1 Eclipse Webmaster

2007-12-04 10:42:49 EST

Ok so there are a couple of caveats to moving from CVS to SVN with the cvs2svn tool that we use. In a nutshell:

1) CVS doesn't record complete information about your project's history. For example, CVS doesn't record what file modifications took place within the same CVS commit. Therefore, cvs2svn attempts to infer from CVS's incomplete information what /really/ happened in the history of your repository. So the second goal of cvs2svn is to reconstruct as much of your CVS repository's history as possible.
2)One of the most important topics to consider when converting a repository is the distinction between binary and text files. If you accidentally treat a binary file as text *your repository contents will be corrupted*.

For more details check out http://cvs2svn.tigris.org/cvs2svn.html 

If your ok with those then we would need to schedule a time when all project committers stop posting CVS commits and then I can move the repo into SVN.

-M

Comment 2 Terran Gilman

2007-12-12 12:21:38 EST

Actually, there is a lot of legacy code in the cvs repository that we would like to not migrate over to the new repository and were planning on doing some major reorganization of the code base.  Can we have the svn repository set up initially blank?  Also, I'd like to keep the cvs repository around until the transition is complete and have a chance to organize the legacy code in an archive section of the new repository.

Comment 3 Eclipse Webmaster

2007-12-12 16:13:11 EST

If all you want a blank SVN repo then we can do that.

-M.

Comment 4 Terran Gilman

2007-12-12 16:24:58 EST

That would be excellent.  Also, I want to make sure that the existing cvs repository will remain intact.  We'll need it for archival purposes for some time to come as we perform our re-org and identify all the legacy components.  Thank you for your efforts.

Comment 5 Denis Roy

2007-12-12 19:49:10 EST

(In reply to comment #4)
> We'll need it for archival purposes for some
> time to come as we perform our re-org and identify all the legacy components.

For ease of management, we ask that projects pick only one repo, but you can certainly migrate over a period of time.  What's your anticipated migration schedule?  1 month?  6 months?

Comment 6 Terran Gilman

2007-12-19 16:54:20 EST

This should only take on the outside a couple of months to get everything organized.

Comment 7 Eclipse Webmaster

2007-12-21 10:00:49 EST

An empty repo has been created in svnroot/technology for org.eclipse.vtp .  I've assigned all currently listed vtp committers to the SVN dev groups, so you should be able to start importing.

-M.

Comment 8 Terran Gilman

2007-12-21 11:29:28 EST

Great news!  Thank you.  Should I update this ticket once the transition period is over and the cvs repo can be removed, or should I open a separate ticket at that time?

Trip

Comment 9 Eclipse Webmaster

2007-12-21 11:40:13 EST

Please open a separate ticket to have your CVS repo closed and archived.

-M.