16:06:21 #startmeeting CCSDK Weekly 12/15/2017 16:06:21 Meeting started Fri Dec 15 16:06:21 2017 UTC. The chair is djtimoney. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:06:21 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:06:21 The meeting name has been set to 'ccsdk_weekly_12_15_2017' 16:06:41 #chairs djtimoney 16:08:13 #topic Beijing release contents 17:03:24 #info Priority for Beijing release is platform maturity. Specific criteria and our commitments can be found in CCSDK Beijing release planning template : https://wiki.onap.org/display/DW/Release+Planning+Template+%3A+CCSDK+Beijing+Release 17:04:45 #info Functional requirements for Beijing release also presented at ONAP developer event : https://wiki.onap.org/download/attachments/20086968/ONAP%20Beijing%20functional%20requirements%20from%20usecase%20subcommittee%20r2.xlsx?api=v2 17:05:04 #info More detail to come on functional requirements 17:06:32 #info Jira filter defined listing current CCSDK epics/user stories for Beijing release : https://jira.onap.org/browse/CCSDK-152?filter=10792 17:06:59 #topic Beijing release schedule 17:08:10 #info Reviewed Beijing release schedule presented at ONAP developer event : https://wiki.onap.org/download/attachments/3246393/ONAP-BeijingCalendarDevelopmentBestPracticesV2.pdf?version=1&modificationDate=1513102092000&api=v2 17:09:08 #info Dan noted that dates on schedule reflect dates of TSC review/approval of milestone. Milestone deliverables themselves must be completed 3 days earlier to permit time for review. 17:09:54 #info Release planning templates for Beijing are due 1/8 - 10 days prior to M1 milestone date. By that date, all epics for Beijing must be defined. 17:10:07 #topic Beijing assignments 17:10:58 #info Dan is reviewing Epics/User stories to verify that user stories can fit in single sprint. Will create initial sprints for Beijing and ask for volunteers via onap-discuss mailing list. 17:11:22 #endmeeting