The code in trunk is always maintained as close to release state as possible. Trunk, branch, and tag are the 3 main divisions in subversion repository. With a team of 10 developers it will be a nightmare in the absence of a proper branching strategy. Meanwhile, simple modifications and patches are requested on a day to day basis in the Version 1.0.0.0.Įssentially, with the changing business needs you are required to do a deployment every other day or so i.e. You envision it will take couple of weeks to get that feature coded, tested and released. Couple of days after the release, you get a request for a new feature that must go as Version 1.1.0.0. Let us assume that on a day to day basis you use agile methodologies such as extreme programming or scrum and you have finally released a reasonably complex project with Version 1.0.0.0.
You may need to adopt branching in many different scenarios.
This blog aims to provide a simple branching and merging strategy to manage the code in a fast paced team development environment. Version control systems play a vital role in the success of a software development team.
0 kommentar(er)
