![]() ![]() We stumbled at times, but eventually we came up with a strategy that’s flexible enough for our client demands, yet more simple than most models. Each addition to the process was discussed, used in the wild for a couple weeks and rediscussed, ultimately keeping it or cutting it. Instead of adopting unnecessary complexity, our team built off of our simplistic approach, adding steps and methodologies as needed. ![]() Without releases, this model becomes overly complex. While tried and true, there’s one element that didn’t line up with the majority of our applications: releases. When asking most people what the ideal branching strategy is I get pointed to A successful Git branching model, also known as git-flow. After taking a simplistic approach we quickly realized our branching model needed another look to allow for development of concurrent features. This is why we switched to Git from SVN over four years ago. When developing applications with multiple features, team members and deadlines, a version control system with robust branching is key. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |