...
- After M4 code freeze, the community is spending a lot of time to get the Health Check sanity test to pass. HealthCheck is the kind of automated test that MUST pass everyday all along the release lifecycle.
- Despite the effort made by some ONAP partners in providing Labs, we have reached the limit on current labs infrastructure. This is preventing further needed testing (like test job during the verify phase).
- Need to develop a full Agile CI-CD pipeline.
- How to make better usage of XCI-CD environment (OPNFV,...)
- CSIT tests under integration repo must branch early to support the other component branches and their test automation (at least must branch on code freeze deadline to provide enough time to fix the CSIT tests in the release branches).
- Supporting HEAT and OOM based deployments is getting harder with duplicate maintenance of the config values (it may help if we can somehow abstract such duplication of config values).
• Release Management
- Progress check between M2 and M4 of intermediate development by release manager might help to improve the quality of the final product (for example scheduling the demos of each component to show the current progress at M3 deadline might be right choice too). This avoids any misunderstanding of the features or requirements by the dev team and can receive feedback from the usecase or architecture teams to improve them when there is still time until code freeze.
• JIRA Management
- Often lack of updated information in "Status" field, that prevent to know if someone is working on a defect. This issue varies depending on project and people.
- Adopt a singe JIRA workflow. Currently 2 are in place (1 from openecomp, 1 simple from openo)
• Code Review
- Requires active committers and more active code reviewers (right now only few committers or reviewers are always reviewing and merging the code).
• Development Infrastructure
...