Page 1 of 1

Bitbucket DVCS???

Posted: Mon Jun 28, 2010 11:01 pm
by alex.barylski
I've been trying to sell myself on the latest/greatest VCS systems out there, Git, BitBucket, you name it. Problem is, as a developer that has rarely worked in a distributed environement (I have mostly used SVN in small teams) the idea of 'social coding' is not enough to sell me on a new technology and drop all these tools I understand well, not to mention mature tools like TortoiseSVN, Trac, etc.

From what I understand:

1. Every working copy contains full revision history. I was sure that's what .svn directories maintained too, so while riding an airplane I could flip back through older revisions, but now that I think about it, I do recall being harassed for user/pass when using svn+ssh each time I accessed the repository. That could be nice. :)

2. Fear of comitting due to broken code. I hate not commiting code frequently because I like to keep changes minimal and comments abundant. But sometimes little changes which work in their own right, break other code and I hate committing non-working code, which makes refactoring a little painful at times. As I understand committing in DVCS like Git makes committing less scary because every working copy is it's own repo, in a sense.

My question then, becomes, if committing is done locally, what is it called when you syncronize to a central server, or does this model of working go right out the window? How do i share (what is it called) when I wish to share all or some of my commits to the rest of the network?

What are some other benefits to making the switch? Twice in the last 6 months I have been asked whether I knew anything about Git and I have had to say, only an introductory understanding. :(

Cheers,
Alex