On 6/12/15 10:57 AM, Corey Osman wrote:
I have been tasked with an assignment to come up with a document for non
technical decision makers to “chose Git over SVN”, since non technical people
view VCS is all the same. With regards to Puppet I think its a horrible idea to
use SVN but how do we prove it for decision makers that have no reference?.
If you have given this argument before or want to add your advice, opinion,
reasons, stories, feel free to clone this repo and merge your input. Spencer
Krum has agreed to put this document into an official puppet community repo
https://github.com/puppet-community once the document reaches a good state.
The idea here is if you encounter this situation in the future there will be a
document to hand to somebody to say “Here read this”. So if you like BeerOps,
check this out (literally).
https://github.com/logicminds/A-Case-For-Git.git
Corey
Being somewhat in the middle of a similar conversation at $dayjob I
believe it's a mistake to focus on the technology rather than the
outcome. I would focus on workflow, integration, and tooling instead.
Particularly the local branch per feature or ticket to review board to
merge to release branch is flexible, powerful, and relatively easy to
understand.
"You'll find yourself about 900x more agile with git or the like" -
Binford2k
Remove. If you want to make this point run a benchmark and link it.
Ramin
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/557B218F.8040809%40badapple.net.
For more options, visit https://groups.google.com/d/optout.
