... | ... | @@ -12,6 +12,23 @@ |
|
|
</tr>
|
|
|
</table>
|
|
|
|
|
|
|
|
|
## Merge Request Workflow Presentation ##
|
|
|
|
|
|
A Merge Request can be created when the code is structuraly stable and reviewable.
|
|
|
|
|
|
Regarding the CI results analysis, the following tests are unstable and may be disregarded, especially if you are working on 5G :
|
|
|
- eNB-CI-IF4p5-TDD-Band40-B210
|
|
|
- eNB-CI-MONO-FDD-Band13-B210 (LTE-M)
|
|
|
- eNB-CI-MONO-FDD-Band13-X2HO-B210
|
|
|
- eNB-CI-TDD-Band40-B210
|
|
|
|
|
|
The developer is primarily responsible for manual inspection an pre-filtering of the CI results.
|
|
|
If any doubt, the CI team is of course available to review the results.
|
|
|
|
|
|
Once the MR is tagged READY_TO_BE_MERGED, developers shall not push again to that branch
|
|
|
|
|
|
|
|
|
## Committee Role ##
|
|
|
|
|
|
The Technical Committee is responsible for the following tasks:
|
... | ... | |