/
2019-05-15 Policy Bi-Weekly Meeting (shared with CLAMP)

2019-05-15 Policy Bi-Weekly Meeting (shared with CLAMP)

May 15, 2019

AGENDA

Duration

Agenda Item

Requested by

Notes / Links

Duration

Agenda Item

Requested by

Notes / Links

START RECORDING

 

Logistics

@Pamela Dragosh

 

 

Scrum

@Pamela Dragosh

 

 

 

 

 

 

 

 

 

 

 

 

 

ATTENDEES

RECORDING:

NOTES

  • RC1 is tomorrow May 16, 2019 and our checklist is getting there: Policy R4 Dublin RC1 Deliverables for RC1 Milestone Checklist Template

  • Congratulations to @James Hahn and @Ram Krishna Verma for committer promotions (pending TSC approval)

  • We need to confirm and close all outstanding bugs - we will re-release artifacts if necessary.

  • Artifact release is in process. See Policy Framework Project: Component Versions

  • Documentation - we have work to do over the next 2 weeks until RC2 May 29, 2019 to finish this.

  • Integration Testing is continuing - please support that team as they have started Control Loop testing.

  • Scale Out use case testing will start end of week and the other use cases are in process (CCVPN and 5G OOF PCI)

  • El Alto Planning is beginning - I am in the process of working with folks to prioritize the Policy Board and determine what resources will be available to help.

    • 4 sprints - pre El Alto sprint and 3 other official development sprints.

    • Think of El Alto as a Dublin Maintenance Release.

      • Only minor features will be supported if resources are available.

      • Please plan accordingly based on potential summer vacations.

    • Highest priority is moving to global-jjb - must be done immediately

    • Healthcheck consolidation

    • S3P Stability and Performance testing

    • S3P Security

    • S3P Logging

    • "Under Promise and Over Deliver"

    • Tutorials and Documentation improvements

    • If you create a user story - please be sure to put an estimate in. Tasks don't have estimate field, so please add into description time estimate.

    • Features can be added if resource is available and the work does not put testing in jeopardy. eg. Deployed dark.

  • June DDF in Sweden - Liam is putting together proposals on that for Policy team.