Community
Participate
Working Groups
Before we can do the termination steps (which I will detail in a follow-up message), we need to move the project code to GMF Tooling (per the Modeling Restructuring document [1]). While we're at it, the code is in a CVS repository that needs to be migrated to Git. If there is no objection, I recommend migrating and moving in one swoop. GMF Tooling already has a Git directory (/gitroot/gmf-tooling). Do you want to move the code into the existing repository, /gitroot/gmf-tooling/org.eclipse.gmf-tooling.git, or create a separate repository (e.g. /gitroot/gmf-tooling/org.eclipse.gmf-tooling.uml2tools.git)? [1] http://wiki.eclipse.org/Modeling/project_termination_review_2012#UML2_Tools
Hello, The most reasonable place would be to have a uml2-tools folder as a sibling to /samples, /plugins, /doc etc here: http://git.eclipse.org/c/gmf-tooling/org.eclipse.gmf-tooling.git/tree/ If it is not an option, then I would like to create a separate repository (e.g. /gitroot/gmf-tooling/org.eclipse.gmf-tooling.uml2tools.git. Regards, Michael
(In reply to comment #1) > The most reasonable place would be to have a uml2-tools folder as a sibling > to /samples, /plugins, /doc etc here: > http://git.eclipse.org/c/gmf-tooling/org.eclipse.gmf-tooling.git/tree/ > > If it is not an option, then I would like to create a separate repository > (e.g. /gitroot/gmf-tooling/org.eclipse.gmf-tooling.uml2tools.git. We know how to make a separate second repository. Merging repositories, however, is something that we don't have a lot of experience with. It seems sort of easy enough: after converting the CVS repository to Git, you can do a subtree merge. http://nuclearsquid.com/writings/subtree-merging-and-you/ Are you able to do this, or do you require webmaster assistance?
What is your status? The CVS deadline is approaching... How can I help?
Sorry, I probably don't understand the procedure well. I can easily live with separate repository at /gitroot/gmf-tooling/org.eclipse.gmf-tooling.uml2tools.git in order to avoid any merging. - Should I create the separate bugzilla for webmaster and generally follow the standard procedure for migration from cvs to git (I have done that for GMF tooling once) - or, as I for some reason assumed, THIS IS the bugzilla that covers migration of the CVS content to GIT as a way of uml2tools termination? Sorry if I am asking a stupid question, it seems that I misunderstood the history of comments in this bug.
I have retired all project committers and have marked the project as inactive. (In reply to comment #4) > Sorry, I probably don't understand the procedure well. We don't have a well-documented procedure for everything. This is sort of a corner case, so we just do what we feel is reasonable. FWIW, I thought that I was waiting for you to answer a question. I'll consider this your answer. > I can easily live with separate repository at > /gitroot/gmf-tooling/org.eclipse.gmf-tooling.uml2tools.git in order to avoid > any merging. Webmaster, can you please migrate the UML2Tools CVS repositories to Git under /gitroot/gmf-tooling? i.e. Migrate /cvsroot/modeling/org.eclipse.mdt/org.eclipse.uml2tools to /gitroot/gmf-tooling/org.eclipse.gmf-tooling.uml2tools.git Migrate /cvsroot/modeling/org.eclipse.mdt/org.eclipse.uml2tools.releng/ to /gitroot/gmf-tooling/org.eclipse.gmf-tooling.uml2tools.releng.git Please also move the project bugs from MDT/UML2Tools to GMF-Tooling/Samples For completeness, there are no CQs associated with UML2Tools.
Done. -M.
It looks like we're done here.
