Branching When Developing New Features

As you saw in this module’s tutorial exercises, it is a good practice to create a new branch for every new feature and bug fix. As a software developer, you are usually assigned work to complete a specific feature or to fix a bug. In this discussion, you will read a short case study and reflect upon effective practices within software development teams.To begin, read the following short case study: https://www.atlassian.com/customers/ames-research-centerWe see NASA implementing the strategy of creating a new branch for each and every new feature and bug fix. Reflect on why this is an effective approach in software development within a team. Why does NASA quickly merge these branches back into the main baseline of code? Finally, think about the role that the history function plays within version control. How does having a record of all past modifications help the developers on a team project?