... | ... | @@ -81,12 +81,13 @@ All issues ready for development, after scope approval, are on the [Development |
|
|
5. QA: doing →
|
|
|
6. Dev: QA fixes → (when relevant, assign back to developer)
|
|
|
7. QA: passed → (ready to be merged to `develop` branch)
|
|
|
8. QA: ncbidev (when relevant, final check on ncbidev)
|
|
|
9. Dev: Done (ready to be merged to `staging` branch)
|
|
|
8. QA: ncbidev (merged to `develop` branch and checked on ncbidev site)
|
|
|
9. Dev: Done (merged to `staging` branch)
|
|
|
|
|
|
* Issues move from "Dev: doing" to "QA: to do" when the assigned developer has completed and tested the functionality in the issue description on the feature branch, this includes writing unit tests when relevant.
|
|
|
* Issues are considered "QA: passed" when the branch has been tested and the integration test is done.
|
|
|
* Issues are considered "Dev: Done" and can be closed when tested on `ncbidev` site and the feature meets the BCMS sign-off criteria in the issue description.
|
|
|
* Issues are considered "QA: NCBI dev" once their MRs have been merged to the `develop` branch, and checked on the `ncbidev` site
|
|
|
* Issues are considered "Dev: Done" and can be closed once their MRs have been merged to the `staging` branch by virtue of merging `develop` into `staging`, have been tested on the `ncbi` site, and the feature meets the BCMS sign-off criteria in the issue description.
|
|
|
|
|
|
#### How we manage branches:
|
|
|
|
... | ... | |