Versioning and branching at their best
December 14, 2018
Versioning and branching at their best
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with Git
We use Git across all of our development projects in order to work on multiple aspects at once and then merge branches as needed. There are four scrum teams and one Kanban team that handles hardware issues. All the scrum teams are developing and maintaining software to various degrees across the organization.
Pros
- It's the best at version control that I've seen. Rollbacks are a snap.
- Provides local control down the individual developer level, which in turn allows easy management back up the chain of command.
- Cloning is perfect when you need to copy a project to tweak it without messing with the main branch.
Cons
- If you're not a developer, it'll take some time to get the hang of it, particularly some aspects of the API.
- Sometimes the parameters are WAY too long.
- As Git is free, any ROI is positive.
- In the higher up levels there is concern about any freeware not being trustworthy, so you might have to fight that mental battle in the boardroom.
Comments
Please log in to join the conversation