Community
Participate
Working Groups
The initial creation of the Vex project under the hoods of Mylyn Docs is finished. Now the "stuff" has to be moved: 1. Move Bugs from WebTools/WTP Incubator/wtp.inc.vex to Mylyn/Mylyn Docs Vex/Core We can move the UI bugs to their correct component "UI" later in another step. 2. Move the code from its temporary home at https://github.com/kingargyle/vex.git to git://git.eclipse.org/gitroot/mylyn/org.eclipse.mylyn.docs.vex.git The restructuring according to the Mylyn directory structure can be done later in another step. 3. Find the relevant IPZilla records and move them to mylyn.docs.vex https://dev.eclipse.org/ipzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=Vex&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=
(In reply to comment #0) > 2. Move the code from its temporary home at > https://github.com/kingargyle/vex.git to > git://git.eclipse.org/gitroot/mylyn/org.eclipse.mylyn.docs.vex.git > The restructuring according to the Mylyn directory structure can be done later > in another step. Uh... "temporary home" ? I thought that this code was in the WTP incubator. If it has been maintained externally, it'll have to be taken through the IP process (i.e. you'll have to enter it as a contribution).
(In reply to comment #1) > (In reply to comment #0) > > 2. Move the code from its temporary home at > > https://github.com/kingargyle/vex.git to > > git://git.eclipse.org/gitroot/mylyn/org.eclipse.mylyn.docs.vex.git > > The restructuring according to the Mylyn directory structure can be done later > > in another step. > > Uh... "temporary home" ? > > I thought that this code was in the WTP incubator. If it has been maintained > externally, it'll have to be taken through the IP process (i.e. you'll have to > enter it as a contribution). All this is is a filtered branch of the wtp incubator items. No code changes have been done, and no new commits. Basically it's a already filtered repository of the process I described in my blog entry. http://intellectualcramps.wordpress.com/2011/09/27/re-writting-eclipse-commit-history/ The exact same process can be run against another clone of the wtp incubator git repository and then the pushed to the new repository for mylyn.docs.vex. Hope that clarifies things.
I've done the move to git.eclipse.org/gitroot/mylyn/org.eclipse.mylyn.docs.vex.git. Unfortunately the it is not possible to clone the new repository anonymously using git clone git://git.eclipse.org/gitroot/mylyn/org.eclipse.mylyn.docs.vex.git This command always results in "fatal: The remote end hung up unexpectedly" This is a problem, because our Hudson builds do not work on the new repository. @Webmaster: Please do also move the builds cbi-wtp-inc.vex and cbi-wtp-inc.vex-integration out of the WTP group. The builds should also be renamed: cbi-wtp-inc.vex -> mylyn-docs-vex.ci cbi-wtp-inc.vex-integration -> mylyn-docs-vex.integration
> All this is is a filtered branch of the wtp incubator items. No code changes > have been done, and no new commits. Basically it's a already filtered > repository of the process I described in my blog entry. Okay. Works for me. Sharon and Matt, please continue.
(In reply to comment #3) > I've done the move to > > @Webmaster: Please do also move the builds cbi-wtp-inc.vex and > cbi-wtp-inc.vex-integration out of the WTP group. The builds should also be > renamed: > cbi-wtp-inc.vex -> mylyn-docs-vex.ci > cbi-wtp-inc.vex-integration -> mylyn-docs-vex.integration Done. We fixed the git issues separately. -M.
I've moved the related CQs via IPzilla. I did not move CQ 3050 which appears to have been included in your search criteria as it appears to be related to the RT project. I'm happy to do so; however, I wanted to double check first that it wasn't included in error. Regards, Sharon
(In reply to comment #6) Thank you Sharon. I don't know how CQ# 3050 came into the search result. It is not related to Vex.
(In reply to comment #7) > (In reply to comment #6) > Thank you Sharon. I don't know how CQ# 3050 came into the search result. It is > not related to Vex. The search criteria matched "Vex" to "nuoveXT". Next time, include a project (i.e. webtools.incubator) to narrow the search. All's well that ends well.
The restructuring of the code is finished now: - all plug-ins, features and releng projects reside in the same directory - the root package is now 'org.eclipse.vex', 'wst.xml' was removed from the package name @Webmaster: Should we make the old git repository read-only, or should the code be completely removed from the old repository?
(In reply to comment #9) > > @Webmaster: Should we make the old git repository read-only, or should the code > be completely removed from the old repository? Where is the old repo? Normally for VCS changes (SVN->Git) we mark the old repo as read only fora few months and then remove it after that. If you think you've got everything we can remove it now and go to tape if we need something. -M.
(In reply to comment #10) > Where is the old repo? Normally for VCS changes (SVN->Git) we mark the old > repo as read only fora few months and then remove it after that. If you think > you've got everything we can remove it now and go to tape if we need something. The old repo is org.eclipse.webtools.incubator.git, but only on the branches vex-dev and vex-release. The WTP incubator also contains other projects, each project has its own branches. We have everything in place, so please go on. There also exist some clones of the repo, just in the case. Florian
(In reply to comment #10) > (In reply to comment #9) > > > > @Webmaster: Should we make the old git repository read-only, or should the code > > be completely removed from the old repository? > > Where is the old repo? Normally for VCS changes (SVN->Git) we mark the old > repo as read only fora few months and then remove it after that. If you think > you've got everything we can remove it now and go to tape if we need something. > > -M. Well, with git, we maintain all the prior history as well of the old repo. Vex is a unique beast because it was extracted out of the WTP incubator main repo, which is currently still being used. However, we are going to be breaking out the wtp incubator projects into their own repos so the old wtp incubator repo will eventually go away.
(In reply to comment #12) > Well, with git, we maintain all the prior history as well of the old repo. Vex > is a unique beast because it was extracted out of the WTP incubator main repo, > which is currently still being used. However, we are going to be breaking out > the wtp incubator projects into their own repos so the old wtp incubator repo > will eventually go away. Dave is right, it would be better to just wait until the old WTP incubator repo is completely obsolete, before deleting the content. I will close this bug because the move of Vex is finished. Thank you all for your help.
(In reply to comment #12) Ok, I'll wait until then. -M.
