[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [xtext-dev] Xtext migrates to Git!
|
On Jul 6, 2010, at 4:01 PM, Moritz Eysholdt wrote:
Hi,
this is what I'm planning to suggest to the Eclipse Webmaster:
comments/resistance?
---
Let's get specific.
- We'd like to migrate as soon as possible.
- Due to the uncertain import situation (1) it seems cleaner to only
import HEAD to git and use the old CVS repository in case we need to
access the history. Furthermore, I still like the idea of getting
rid of historical ballast.
- We need *six* repositories:
- org.eclipse.xtext.git
- org.eclipse.xtext.releng.git
- org.eclipse.emf.mwe.git
- org.eclipse.emf.mwe.releng.git
- org.eclipse.xpand.git
- org.eclipse.xpand.releng.git
(warum muss da überall das 'git' suffix dran sein?)
- They will be fed from
- http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.tmf/org.eclipse.xtext/?root=Modeling_Project
- http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.tmf/org.eclipse.xtext.releng/?root=Modeling_Project
usw.
- We would like to use CVS and git in parallel for some time. By
parallel I mean write access to git and CVS. It will be our
responsibility to keep CVS and git synchronized - we'll probably do
so by applying the same patch to both repositories. I can also think
of applying all changes to git and only the critical bugfixes to
CVS. This is because we haven't migrated our build infrastructure to
git yet and we need to have a writable repository + integration
build at all times. As soon as the build and working with git seems
reliable, we'll ask to turn the CVS repository read-only.
Yesterday we discussed to have the git repository as a playground in
order to get the builds up and running while the CVS remains the
production repository.
Then at some point when we are comfortable with the new environment
(and the builds are running) we could replace the git repos with the
latest from CVS head. Why don't you want to do this anymore?
Sven
