[Kde-scm-interest] svn, git, bzr

[Thomas Zander]

On Monday 21. July 2008 20:08:09 Stephen Kelly wrote:
>  Or is it seen as a pointless exercise as many kde developers
> already use git?

I won't comment on pointless. I won't tell you to stop doing what you like to 
do :)
I can give you one datapoint that may provide some food for thought;

some time ago there was a nice blogging rage. People run;
history | awk '{a[$2]++}END{for(i in a){print a[i] " " i}}' | sort -rn | head
and post the results.

Peoples results were posted on various gnome and kde blogs. One thing that 
shows up for any programmer is some sort of scm.  Sometimes two ;)
I noted that git was used by the fast majority of the users that didn't have 
svn in there, bzr was posted in one too.


To the question that inevitably comes up in these threads of what the 
advantage is of one scm over the other I typically answer that git is the one 
tool that actually does not dictate any workflow. Its flexible enough to 
adjust to your workflow.
Some people start using git and get lost exactly because of this, they don't 
find guidance on optimal workflow from git.
So for KDE I think we should largely decide upon a workflow we can suggest to 
people.
The devs that disagree can still use gits power to choose any other workflow 
that suits them better.

-- 
Thomas Zander
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-scm-interest/attachments/20080723/66ae638d/attachment.pgp