Re: [xtext-dev] Xtext migrates to Git!

[Sven Efftinge <sven.efftinge@xxxxxxxxx>]

> > > - 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.

Yes, I think that would be better, as we maintaining two repositories  
(CVS and git) for a couple of weeks seems to be tiresome.

Sven