More than 3000 questions in repository. There are more than 900 unanswered questions. Click here and help us by providing the answer. Have a video suggestion. Click Correct / Improve and please let us know.
Ans. We creates separate branches for each project if development work is going on parallel and they are to be released at different times. Once the first release is done, we merge the branch changes into trunk. If they all have to go at one time, we usually would merge everything in the trunk itself.
Help us improve. Please let us know the company, where you were asked this question :
Q3. Is it advisable to just hold checking in your changes to trunk if there is another release planned in between ?
Ans. If it's just smaller change, and single person is working, then this approach is fine. Otherwise there are risk on loosing it on your machine. Moreover , If there are multiple people working , it makes it hard to share code. It's better to create a separate branch and then merge it later to trunk.
Help us improve. Please let us know the company, where you were asked this question :
Ans. We have followed this practice in one of the project. The only downside we felt was the need to merge the new snapshot version to master after the release.
The Benefit is that it's easy to just ignore the branch if complete rollback happens and hence master remains in sync with production.
Help us improve. Please let us know the company, where you were asked this question :