[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [rap-dev] Git Timeline
|
Hi Ralf,
Unfortunately, the EGit tooling is not as mature as the CVS team
stuff, especially when it comes to synchronization, which is IMHO the
most critical step in the workflow.
I am onboard with that....I am debugging the EGit synchronization
process as we speak....it really needs some work.
Here is the migration bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=331780
My plan was to keep the GEF port up to date with GEF HEAD as we go, but
I will probably wait until we migrate the repo for that.
But for now, I will check in the port for GEF at the state of GEF HEAD
when I check it in, and then update it once more manually for the Indigo
release.
On 12/3/2010 10:05 AM, Ralf Sternberg wrote:
Hi Austin,
I can't wait to move over to Git, I think we're all eager to change.
Unfortunately, the EGit tooling is not as mature as the CVS team
stuff, especially when it comes to synchronization, which is IMHO the
most critical step in the workflow. Another problem I see is that we
might lose some folks who are now working with RAP from CVS and aren't
yet familiar with Git. To my knowledge there is no easy way to fake a
CVS from a Git repository. So we should discuss this change on the
newsgroup and announce the change early.
My suggestion would be to wait until after the Indigo release. Until
then EGit has hopefully become usable. And if we really start working
on a version 2.0 then, wouldn't it be perfect to start this work in a
brand new Git repo and keep 1.x in CVS?
Since you asked, would you like to open a bug to track progress on that?
BTW, I just found this Git Migration Guide in the wiki:
http://wiki.eclipse.org/Git/Migrating_to_Git
Ralf
On Fri, Dec 3, 2010 at 16:08, Austin Riddle<austin.riddle@xxxxxxxx> wrote:
Does anyone know what the timeline is for a writable Git repo for RAP?
It would make maintaining the ports MUCH easier.
