Explore >> Select a destination
|
You are here 
|
ryanharter.com | ||
| | | | |
nvie.com
|
|
| | | | | In this post I present a Git branching strategy for developing and releasing software as I've used it in many of my projects, and which has turned out to be very successful. | |
| | | | |
www.cheehow.dev
|
|
| | | | | Simple Git branching strategy for small teams. | |
| | | | |
www.craigpardey.com
|
|
| | | | | I've been working on re-platforming the online banking system for a Canadian retail bank for over two years. Leading up to the initial launch, The Business decided to defer a few features to the next release which was scheduled for about a month later. We created a release branch to support defect fixes found in testing, and the development team continued adding features to the develop branch. Bug fixes from release were merged into develop regularly. The process was working. | |
| | | | |
www.blopig.com
|
|
| | | |||
