On 3/20/2012 8:52 PM, Julien Nitard wrote:
Related, I like to test branches and ideas without having anyone else observing my moves or caring about what I do; so, I can do that, locally, instead of creating obscure or sacred branches in SVN in a common repository.
This is a very good point. Though it is still a specific need. The VCS is here to help the team. If individuals want to play on their own, it's only "nice to have" IMHO and shouldn't make the other part of the process more complex.
I would argue that "hiding" changes is detrimental to software development. In particular it prevents sufficient software auditing and accountability. It would also curtail active review of the work such that it could end up that one would waste time pursuing development avenues that others have already discounted. Because they would not see the path you are taking and warn you about the cliff you are about to walk off into. Hence I would be suspect about a VCS that "encourages" or "facilitates" the practice of sequestering work. That is I don't consider non-accessible branching as a qualified value proposition for DCVSs (or more accurately termed replicated VCSs -- but that's just semantics ;-). -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail