Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 366731 - Nebula requests migration from CVS to Git
Summary: Nebula requests migration from CVS to Git
Status: RESOLVED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Git (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Eclipse Webmaster CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-14 12:44 EST by Mickael Istria CLA
Modified: 2011-12-16 10:09 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mickael Istria CLA 2011-12-14 12:44:00 EST 
The Nebula project team has agreed to process the migration from CVS to Git as soon as possible.
See http://wiki.eclipse.org/Nebula/Minutes and http://dev.eclipse.org/mhonarc/lists/nebula-dev/msg01597.html for more details about the discussion.

The CVS is ready to be made read-only, and committers are ready to welcome the new Git repository for Nebula.

Can you please perform the migration?
Comment 1 Wim Jongman CLA 2011-12-14 15:40:12 EST 
We would like to import with full history. We also want to restructure the repository according to the following structure:

bundles
  widget
     o.e.n.widgets.widget
     o.e.n.widgets.widget.feature
     o.e.n.widgets.widget.tests
     o.e.n.widgets.widget.tests.feature  <-- really needed?
     o.e.n.widgets.widget.example
     o.e.n.widgets.widget.snippets

Does this need to be done _during_ import or can we do it after the complete repository is imported?
Comment 2 Eclipse Webmaster CLA 2011-12-14 16:19:02 EST 
We recommend that any restructuring be done before/after the conversion.  The import tooling isn't really able to handle it.

Let me know about the restructure and we'll get this underway.


-M.
Comment 3 Wim Jongman CLA 2011-12-14 18:06:37 EST 
(In reply to comment #2)

> 
> Let me know about the restructure and we'll get this underway.

Do you mean that you help us do the restructure or that you wait for the decision to do it before or after the conversion. 

> We recommend that any restructuring be done before/after the conversion.  The
> import tooling isn't really able to handle it.

since CVS does not allow restructuring (afaik) we must do it after the conversion.

Thanks

Wim
Comment 4 Mickael Istria CLA 2011-12-15 08:30:44 EST 
I think it will be easier and safer to perform migration first and then restructuring on Git, because our current CVS does not record history of move and deletion of files (ie restructuring).
Comment 5 Eclipse Webmaster CLA 2011-12-15 10:40:38 EST 
Ok, I've created /gitroot/nebula and have done an initial import into org.eclipse.nebula.git .  If everything looks like you expect I'll lock down CVS and schedule it for clean up in a few months.

-M.
Comment 6 Mickael Istria CLA 2011-12-15 10:56:17 EST 
Once again, you performed a great migration! Please make the CVS read-only.
Comment 7 Eclipse Webmaster CLA 2011-12-15 11:01:59 EST 
OK, glad everything has worked out.  I've marked the CVS read-only and I'll add it to the cleanup list.

-M.
Comment 8 Chris Aniszczyk CLA 2011-12-15 11:21:57 EST 
Remember to update your portal.eclipse.org project metadata :)
Comment 9 Mickael Istria CLA 2011-12-15 11:24:33 EST 
That's already done!
Please ping us when we can enjoy the Nebula mirror at GitHub ;)
Comment 10 Wim Jongman CLA 2011-12-16 10:09:47 EST 
Thanks -M. for getting this done so quickly. In the mean time we have restructured the repository with great ease. A couple of git mv actions did the trick.