Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • So today I talk to one of my former colleagues and I tell him that I'm trying out git and svk and how it is going to solve my problems. He said it sounds cool but it would probably never fly in a corporate environment where they want everything centralized so it can be controlled, backed up, etc.


    As you suggest, this is a common way to miss the point. With distributed version control there can still be a central, canonical repository that can be backed up, controlled, etc. There's also always uncontrolled stuff on the developers' workstations. Of course, you can back that up, too, if you back up their workstations -- and that remains the case with svk or git, but now their work can be reintegrated to the core mind as a set of changes, rather than a lump.

    To explain distribued VC in a corporate environment, I think the proper buzzwords are "work offline" and "team-based collaboration."
    --
    rjbs