Re: [Cs-studio-core] cvs to mercurial migration

[Hatje, J. <jan...@de...>]

Hello,

Because we are now very busy with our new CSS version I have had few
time to test the headless build with mercurial. But I suppose that your
demo repository css-cvs2hg-simple makes the Hudson test easier because
we can use the most of the current configuration.

I will add the plug-ins for our CSS product to the migration list. But I
have to add ca. 100 more plug-ins. Do you think we should split the
application folder in application-common, application-nsls2,...?

Best regards,

Jan 

	-----Original Message-----
	From: Shroff, Kunal [mailto:sh...@bn...] 
	Sent: Wednesday, June 30, 2010 2:40 PM
	To: cs-...@li...
	Subject: [Cs-studio-core] cvs to mercurial migration
	
	

	Hello,

	 

	I wanted to pick up the discussion regarding the migration of
the css repository from cvs to hg.

	We have set up a method to successfully convert the cvs
repository to mercurial with the history. While hg convert was useful
for smaller conversions (I used it to convert databrowser and boy) for
converting the entire repository indirect conversion using git cvsimport
proved easier, It overcame certain cvsps errors.

	 

	Using this we have converted the entire css-core and
css-applications directories from the desy repository and published this
example on sourceforge
(http://cs-studio.hg.sourceforge.net/hgweb/cs-studio/css-cvs2hg-simple)
. I intend this repository to only be a demo for us to look at how the
imported history looks (and check if all of it gets through the way we
want it). 

	 

	I have also created a wiki page
(https://sourceforge.net/apps/trac/cs-studio/wiki/MercurialMigration)
with a list of plugins and features organized according to the new
architecture. I have only added the plugins and features currently being
used by our product. The first step for the migration would involve
adding all the plugins and features required by our respective products
to the appropriate lists - using these lists we can then create the new
mercurial repository. We could use this step as the first round of
cleanup - avoiding addition of unnecessary plugins would ensure that the
history does not get too big.

	 

	Sincerely

	Kunal