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

[Carcassi, G. <car...@bn...>]

> Seems to me that we have multiple demo setups on SF...
Sorry for the confusion. Let's see if I can clarify.

We (Kunal and I) are expecting from someone at Desy (Jan?) and someone
at SNS (Kay?) to have a look at css-cvs2hg-simple and tell us:
1) Whether the CVS->HG conversion happened to their satisfaction
2) Fill in the list of plugins they want to move on the wiki at
https://sourceforge.net/apps/trac/cs-studio/wiki/PluginsAndFeaturesList.
Plugins that are not put there, are not going to be brought over to
minimize the size of the repository.
3) Tell us what to do with the branches: we drop them? Do you want them?
Do they need to be merged?

Once we have that information, we will create the "css-main" repository
and junk the rest. At that point I think your plan sounds good: we give
a month time to test and correct it. But first we'd like the information
above.

To expedite the process: do people see useful organizing a phone meeting
where we actually do some (if not most) of the work?

Gabriele


-----Original Message-----
From: Kasemir, Kay [mailto:kas...@or...] 
Sent: Friday, July 02, 2010 12:28 PM
To: cs-...@li...
Subject: Re: [Cs-studio-core] cvs to mercurial migration

Hi:

What is our time line for moving to Mercurial/SF?

Fundamentally, I think
 css-cvs2hg-simple/css-core
 css-cvs2hg-simple/css-applications
looks OK, except for quirks: Why are there CVSROOT directories? In
css-applications, the top-level files .classpath, .project, ...,
plugin.xml seem to be out of place.

How does this fit with the css-repo-strawman?
Does css-repo-strawman represent the overall layout
 build/
 core/
 applications/
 products/
but with only a few actual plugins? On the other hand, css-cvs2hg-simple
has a fully populated list of core and applications plugins, but lacks
the 'build'?


Seems to me that we have multiple demo setups on SF, but none are
complete and their name already indicates that they're not what we want
in the end.

How about this:

BNL sets up _THE_ repository with the final name and layout. For example
called "cs-studio", not simple, strawman, ....

It includes all that you think it should include.

It imports plugins from DESY CVS. Maybe it actually includes the CVS
history, but if a lot of time and space can be saved, maybe it only has
the latest snapshot.
It works for building the NSLS2 product.

Other sites can look at that, try it, comment, but we don't write to it.
When we don't like something, BNL can totally re-create it from scratch
according to suggestions. We're in a phase of creating the setup, not
using it.

In about a month, we then switch over to using that as the shared
repository where others can also write/change.

Would that work?

Thanks,
Kay








On 7/1/10 07:12 , "Carcassi, Gabriele" <car...@bn...> wrote:
> The site specific plugins already go under product/feature, so they
are
> already separate. We were thinking of keeping all the other
applications
> plugins under the same level because ...

> From: Hatje, Jan [mailto:jan...@de...]
> Because we are now very busy with our new CSS version I have had few
time to
> test the headless build with mercurial....

>> From: Shroff, Kunal [mailto:sh...@bn...]
>> I wanted to pick up the discussion regarding the migration of the css
>> repository from cvs to hg.
...
>> 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

------------------------------------------------------------------------
------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Cs-studio-core mailing list
Cs-...@li...
https://lists.sourceforge.net/lists/listinfo/cs-studio-core