![]() At the end of the month, the version can be released and QA gets the next version from the developers. During this time, any found issues are fixed. Then QA has one month reviewing the release. The devs spend one month preparing the next release. This assumes that there won't be any huge problems that would result in a feature from being rejected completely, so you do need some testing long before.Ī release-oriented QA process can work very well with semi-frequent but regular releases, e.g one release per month. If QA finds problems, you can fix them on the release branch which is later merged back into the develop branch. In a release-oriented QA process, a release branch is started and QA reviews that state. This opens two opportunities where QA can be performed: QA can either be done release-oriented or feature-oriented. The development branch represents those features that should be part of the next release. The popular “git flow” you mentioned is concerned with products that have clear releases and largeish features that are developed independently. ![]() Which Git branching model you should choose depends completely on the development process you want to use. But where is a space for QA and option they will refuse some of feature? What then I need to change in the diagram? I apologize for English, I do what I can. From develop branch to the release branch and then from release branch to the master (I don't care about hotfixes right now - they are pretty clear). In another words, according diagram all new features (i.e. Now I'm confused about where to merge them? To do develop branch? If so, what happen when QA refuses only two and I have already merged all five features? I would like to keep separating features in my own branches but I would like to use a pull request to see the diffs and type comments but again then there is a problem in which branch to merge? For example, I have five new features, each of them is in my own branch and I want to give these features to testing. I think I understand how this git flow works but I'm still not sure about testing. We would like to use Driessen's git branch model but we also have QA side.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |