#onap-sdnc: CCSDK Weekly 12/15/2017

Meeting started by djtimoney at 16:06:21 UTC (full logs).

Meeting summary

  1. Beijing release contents (djtimoney, 16:08:13)
    1. 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 (djtimoney, 17:03:24)
    2. 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 (djtimoney, 17:04:45)
    3. More detail to come on functional requirements (djtimoney, 17:05:04)
    4. Jira filter defined listing current CCSDK epics/user stories for Beijing release : https://jira.onap.org/browse/CCSDK-152?filter=10792 (djtimoney, 17:06:32)

  2. Beijing release schedule (djtimoney, 17:06:59)
    1. 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 (djtimoney, 17:08:10)
    2. 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. (djtimoney, 17:09:08)
    3. 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. (djtimoney, 17:09:54)

  3. Beijing assignments (djtimoney, 17:10:07)
    1. 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. (djtimoney, 17:10:58)

Meeting ended at 17:11:22 UTC (full logs).

Action items

  1. (none)

People present (lines said)

  1. djtimoney (14)
  2. collabot (3)

Generated by MeetBot 0.1.4.