We are currently looking into Git as an alternative to Subversion. Interested in coming along?
A very nice, although fast-paced, introduction to git is http://gitcasts.com/posts/railsconf-git-talk
This is about git on Windows, from the same guy: http://gitcasts.com/posts/git-on-windows
Now, practical stuff. As long as everything is still in Subversion for us, using git's built-in Subversion bridging is cool. Just read this to get started: http://www.viget.com/extend/effectively-using-git-with-subversion/
I did that for PHPCR and TYPO3CR last week to be able to branch for some experimental stuff I'm doing, and that works beautifully. Creating a branch, committing to that branch, switching back to master, changing something there, committing that to Subversion. All worked well.
Most impressive is the speed with which all that happens (aside from the svn commit). Looking at the history? Diff? All lighting fast.
Granted for the Mac there is GitX, a nice frontend. But git comes with built-in GUI tools as well, git gui and gitk. TextMate has very complete Git bundle, and there is EGit for Eclipse (still rough). And TortoiseGit.
That might be helpful. I hope. :)
tribble | 20.03.2010
I love git. Would not want to do without it ever again. Best part is, that you can commit anytime you want and upload your commits to a centralized repository in a batch. GitX is nice to get a quick overview and to quickly stage changes that happened in the same file, but belong to separate commits. You will probably stil use the command line alot :D
Adam | 15.02.2015
Our suegsgtion to use tags is just a suegsgtion for a simple way to improve the process. A more complex solution would be to have translation branches in the translation tool. This would map better to our (the developers') workflow, but I imagine it would complicate the interface. It may be difficult for translators to get their heads around the concept of multiple branches. My gut feeling is that tagging would be good enough for developers, and familiar enough for translators.We typically translate as early as possible, which is usually during staging. If we pushed live, and then translated, we could always rely on the master being the only branch that needed translating.Also, no problem at all with the repost. I'm glad you liked it!
Honney | 29.03.2016
That's a smart way of thknniig about it.