September
#AGREED The TSC approve of the Montreal release schedule as shown on v. 7 of the Montreal planning page.
#AGREED TSC agrees to approve to move forward with release planning for Montreal
August
#AGREED TSC agrees to recognize both candidates for Citizenship award for the London release.
#AGREED TSC agrees to highlight themself as in attendance starting next week's TSC meeting August 17th.
#AGREED The TSC agrees to the proposed changes to streamline
#AGREED TSC agrees to Gerrit being down for about a hour immediately following today's TSC meeting
#AGREED TSC agrees to merge changes to remove failing jobs in Docker
July
#AGREED The TSC agrees to allow RELENG to alter sdnc/oam by removing the existence of large binaries from the repo history permanently to allow the mirror replication to happen. (Additional details here).
#AGREED The TSC has approved the Sign Off of the London release.
June
#AGREED The TSC approves changing the London Sign Off to July 6.
#AGREEDThe "O" release will be Oslo rather then Odessa
#AGREED The TSC approve the extended proxy of Byung-Woo for Magnus until the next election.
#AGREED The TSC agree to add the term "intent-driven" to the new mission statement to read as below:
"ONAP is also an industry collaboration to define, describe and evolve a reference architecture for real-time, policy-driven or intent-driven orchestration, management, and automation of physical, virtual, and cloud-native network functions."
#AGREED TSC approves adding the term "intent-driven" to the ONAP mission statement.
#AGREED the TSC approves the following scheduling changes
- London RC rescheduled for June 15
- London Sign Off rescheduled for June 29
- Montreal M1 rescheduled for July 13
May
#AGREED The TSC approve rescheduling the London RC milestone to June 1.
#AGREED TSC agrees to adopt the proposed new direction for ONAP and update the charter to reflect new mission below:
"ONAP is an open-source project containing a set of autonomous components for orchestration, management, and automation of network and edge computing services for network operators, cloud providers, and enterprises.
The components are designed by self-organising projects, evolving in dialogue with code consumers, as well as adhering to ONAP’s global requirements and best practices. To increase the value of the components to the consumers, use cases are identified to guide the bundling of components into packages and integrating components for proof of concept demonstrations.
ONAP is also an industry collaboration to define, describe and evolve a reference architecture for real-time, policy-driven orchestration, management, and automation of physical, virtual, and cloud-native network functions."
#AGREED TSC agrees to change the timing to begin the nominations as soon as we hit the RC milestone.
#AGREED TSC agrees to Combine ARCCOM and requirements review process.
#AGREED The TSC agree that the requirements for M4 have been met, with the exception of the AAI, DCAE, and OOF projects.
#AGREED The TSC approve the proposed schedule (https://wikilf-onap.onapatlassian.orgnet/wiki/x/HoupCQ3gz8 v.3) for the Montreal release.
...
#AGREED The TSC approve of the proposed London release schedule, as shown here (London schedule, confluence v.9 last updated Jan 5)
...