...
- Resolved: That the TSC approves for the Frankfurt release, as exceptions to the Intellectual Property Policy in the ONAP charter, the non-Project Licenses described in the license scan report attached to the email https://lists.onap.org/g/onap-tsc-private/message/1020 distributed to the TSC on May 28, 2020; excluding the exceptions described as not requested or required in the attached report.
- #AGREED: the TSC signs-off on the Frankfurt release based on the following conditions
#1 Feedback from PTLs about new issues CCSDK-2425, CCSDK-2399 and Policy-2631 by June 12th EOD - work around on top of RC2 dockers and/or new patch post-Frankfurt Self-Release
#2 UseCase/Functional reqs owners to confirm by Monday June 15th that they maintain their requirements or not, accepting the risk that final regression on RC2 dockers will continue after the sign-off
TSC 2020-06-18 #AGREED anybody can build a POC. It is always appropriate to share the intent of the PoC with the TSC early to facilitate inclusion in a future release.
- What's important is to follow the guidelines to prevent breaking what has already been committed to that release.
- A PoC should not be incorporated into the CURRENT release. Approval for an inclusion exception from the TSC is required if a PoC decides they want to be converted to be CURRENT release content
- There is no deadline to list a PoC into the release requirements page ( Guilin Release Requirements cited as an example)
- PoCs cannot generate any regression issues.
- Successful PoCs from a PREVIOUS release require a commitment of resources and integration team review if requesting incorporation into the CURRENT release.
May
TSC approved to cancel the TSC call on May 21st, 2020 (Ascension Day) - https://lists.onap.org/g/onap-tsc-vote/message/1512
...