There is a long term release branch of the current method employed in our company, which we develop on all of the non-AB exam codes Both branches are in the same trunk, whereas AB test code is only checked in the branch. Then, once we stay, the winning test cells are merged into the trunk, while most AB test codes are thrown away. This is working for us for some time, but we are starting a new project. And I am thinking that we can be able to improve our workflow with this new project. Everyone is having pain due to checking in both the branch and the trunk. Ideally, we have a more standard approach to the development of branches for the trunk and stabilization, but this means that our tests need to be pollinated with the AB test code.
Comments
Post a Comment