[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- From: Wim Jongman <wim.jongman@xxxxxxxxx>
- Date: Mon, 14 Jun 2010 20:11:36 +0200
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=I0R6fBZZNw9lvCEOP+FpmHzs7EhZ3GL5mT4suPcxWMZnLzYOmEPm3lz+7BwZhxsRWP 04zTLnhIlOvr128TfBLXTXl9bgAmzi9RD/fk6qKIvpYr72LxOQ9tbZ/7mdWQ/TX5ZKHj gO4JwuTD/TKl0IX0HIy64ekwSchBwMdTMzHSI=
We have discussed the move to GIT on the conference call. We have agreed to move to GIT as soon as possible. There are a couple of things that need to be solved in our way of working which we can discuss here:
One advantage of GIT is to have a staged repository. This means that check-ins do not pile up in your workspace but that you can frequently commit in your local repository. This sounds good but it comes with its own sets of threats. For example, programmers tend to become more isolated because their work is not frequently merged to the master repository (if somebody again says there is no master repository, I start screaming ;). Also, if the programmer loses his/her local disk then a lot of changes can get lost because of local only check-ins. In contrast check-ins to CVS HEAD require high quality bites of code which forces the programmer to think/work like that.
Markus suggested to have some kind of intermediate repository (lets say TEST) where work can be merged and build without breaking the build on the master repository. This could even be automated, when the TEST build succeeds, all changes are released to the master repository.
We have talked about the lack of eclipse integration. The CVS state-of-the-art is not available in GIT yet but better integration and adoption rate should run parallel. I have worked on some issue a few months ago in EGit and they have a really committed team. I expect that GIT integration will become better real quick.
GIT also allows us to use code reviews tools like Gerrit. We have to ask the GIT team how this increases the workload, but a bug in one of my own contributions was caught early this way so I can state from personal experience/shame that this works.