Agenda Topics:
Project Status in Guilin Release
Guilin Impact View per Component
Guilin release - non-functional requirements proposed list
New:
Guilin Exception Request for SO
Service Orchestrator Guilin Release M4
RC2 Criteria
Blocking issues :
License scan issues:
SO-3292 - Getting issue details... STATUS
https://gerrit.onap.org/r/c/oom/+/111328
SO-3243 - Getting issue details... STATUS
SO committer promotion:
Way forward for Honolulu:
What went wrong:
- Communication with OOM was not effective
- OOM delays impacted SO feature delivery delays
- • Master branch was not stable because a lot of features and Java 11 upgrade and certificate issues
- • Some testing required additional OOM changes
- • OOM best practices were not broadcasted to the feature teams
- • Security best practices / guidance came out in the middle/late of development cycle
- • Image release number changed multiple times during the Guilin release
What was good:
- The team could come out of the difficult time and meet the target
- Response time from SO team was really good
- In the end the issues were are fixed a release was fix.
What can be improved:
- Reduced code fragments (new projects on the gerrit) for build
- Introduce the gating as part of the jenkins verification process (2 edged sword to deal with, work with the details).
- Increase in auto verification
- • OOM best practices / guidance should come earlier and documented