[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] git migration for ECF

Thanks that looks good.

On Tue, Jul 27, 2010 at 12:34 PM, Campo, Christian <Christian.Campo@xxxxxxxxxxxx> wrote:

FWIW.....I can recommend smartGit (http://www.syntevo.com/smartgit) as client for all the stuff with Git that you need next to egit. Its a java standalone swing client based on jgit and has the full function set of git (as far as I can tell)

- christian

Am 27.07.2010 um 11:54 schrieb Wim Jongman:

+1 for git. After all, sorting out programs that almost work is what we do..

On Tue, Jul 27, 2010 at 12:53 AM, Scott Lewis <slewis@xxxxxxxxxxxxx> wrote:
Hi Folks,

As some of you already know, Markus Kuppe has moved the codebase formerly at the OSU Open Source lab (i.e. CVS at ecf1.osuosl.org) to github.org [1].  Markus is working through the build changes (the builder is Hudson+Buckminster) to build these components.

In addition, we should probably move the dev.eclipse.org ECF codebase over to git (as the primary version control system) as well.  Here [2] is the associated bug.  Markus has brought this move up on this list [3].  The Eclipse Foundation is now making available git repositories hosted at http://git.eclipse.org [4].

Once we move the ECF project contents at dev.eclipse.org to git, it means that committers and contributors (anyone who needs *write* access to the repository) *must* use Git clients for committing and pushing code changes and/or additions/contributions.  The Eclipse eGit project [5], is coming along nicely, but as those of you who have tried it will likely attest, it's not out of incubation yet (0.8 with Helios), and so doesn't have all functionality that the Eclipse CVS client has.  For me, it's necessary to use eGit (recent/nightly builds), *alongside* some command line git client.  I happen to use msysgit [6], and it works ok IMHO...at least for the things that I can't yet get eGit to do.  See the progit book [7] for other alternatives.

The main question to you, the committers, contributors, and community is this:  is everyone ready for moving to git as the primary version control system for the ECF project?  If we are going to do this, it should probably be soon (i.e. before mid August), as realistically the move will destabilize our build for a while, and it will take everyone some time to get fascile with using git for team development.  But as I said, the eGit Eclipse client is not yet out of incubation, so there *will* be inevitable churn associated with this move...and I just want to git (sic) everyone's input about whether others feel they are ready before going ahead with the move (btw...just so everyone is aware...even after the move, read-only access/anonymous access will be available via both CVS and git, so we're only talking about *write* access requiring git clients).

As for me, I think now is a good time to do this, as we don't having a looming release (actually, we need to discuss the timing of the ECF 3.4 release in another thread), and Markus is on a roll :).  And the more time we have to get used to git (i.e. the commit/push workflow), the better.

Other thoughts, opinions, etc on timing of this move?



[1] http://github.com/ECF
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=319948
[3] http://dev.eclipse.org/mhonarc/lists/ecf-dev/msg03860.html
[4] http://wiki.eclipse.org/Git
[5] http://www.eclipse.org/egit/
[6] http://code.google.com/p/msysgit/
[7] http://progit.org/book/
ecf-dev mailing list


compeople AG
Untermainanlage 8
60329 Frankfurt/Main
fon: +49 (0) 69 / 27 22 18 0
fax: +49 (0) 69 / 27 22 18 22
web: www.compeople.de

Vorstand: Jürgen Wiesmaier
Aufsichtsratsvorsitzender: Christian Glanz

Sitz der Gesellschaft: Frankfurt/Main
Handelsregister Frankfurt HRB 56759
Ust-Ident.-Nr: DE207665352

ecf-dev mailing list