[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [xtext-dev] Xtext migrates to Git!
|
When is the repository write accessible?
Am 06.07.10 18:31, schrieb Moritz Eysholdt:
Hi Sven,
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
ok, then let's care about them all at once.
(warum muss da überall das 'git' suffix dran sein?)
it's a common pattern to show off that a certain directory is a git
repository. See also: http://git.kernel.org/ and http://git.eclipse.org/
- 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?
Yesterday we were discussing a git server which would be hosted by
itemis and purely designated to be a playground.... anyway, we can
treat it the same for the git repository at eclipse.org.
If we (re-)import CVS HEAD at some later time, we should make sure to
include at least all revisions since the Helios release. It think it's
valuable to have the source code available in git as it was released
with Helios since many bug reports and support requests we will be
based on this version. Having it tagged in git would make it trivial
to switch one's workspace to this version.
regards,
Moritz
Sven_______________________________________________
xtext-dev mailing list
xtext-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/xtext-dev
