Lesson Learned

Retrospective

Identification of issues - earlier than later

• Pair-wise testing performed by the project teams

• 72h stability test run

• Communication – Wiki, Mailing Lists, IRC

When you are a mailing list moderator do not approve subscription requests from accounts with obviously pornographic domain names. (yes, this really happened. recently.)

• Labs & Test Environment

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).

• Release Management

• 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

• Development Infrastructure

The LF toolchain that is currently in place, do allow to merge in master code that has not been thoroughly tested. This leads to massive disruption in the testing.
Nexus 3 slowness. This has been impacting Integration Team tremendously as it tooks 3-4 more times just to download Docker images.

• PTL Role

• Architecture

• Open Source Values

• Others