Date

13 Jun 2019

Goals

El Alto Release Management Proposal

Discussion items

Compressed cycle and a mid cycle release
Moving from wiki checklists to JIRA Epics and Stories
Suggested priorities
- groom backlog - 2 week window to do clean up
  - Epic - CVEs to be fixed in Sprint 1 to meet 60 day window for CII badging
  - Epic - Documentation
- work on CI/CD improvements
Early Drop
- security fixes -
- don't break the build
- wave 1 != sprint 1
- Wave 1 SDC, SDNC, SO, DMaap, AAI - instantiate MUST work at the end of Wave1
- Wave 2 APPC, Policy, Clamp, OOF, DCAE
- Wave 3 everything else
cl664y@att.com need to understand what blockers to usecases exist.
Q: Multi-arch support? A: requires gobal-jjb move first. July 18 deadline for that.
Q: what does early release mean with regards to repos? A: early drop on nexus
- tagging versus branching?
- test automation is a pre-requisite for integration team - requires PTL support
Paweł Pawlak security issues
- OSJI tickets to solve pen test results top priority
- FREEMAN, BRIAN D raises concern over java upgrade from v8 - concerns also raised around stability of ODL Sodium
- updates to known weak libraries and replacement of those with no fix
- Update CII badging answers
- Eric Debeau need to ensure appropriate info is documented
- also need to remove on-line dependencies
  - FREEMAN, BRIAN D recommend just starting to pen jiras for on-line dependencies
  - Offline install team should have the data needed for this
- Dan Timoney would like to see tighter control of who can set fix-version in JIRA and /or set high/highest bugs

Action items

FREEMAN, BRIAN D Eric Debeau send recommendations on "Waves" to Former user (Deleted) Due: 27 Jun 2019
Dan Timoney branching vs tagging stat at the ptl call 17 Jun 2019
Bengt Thuree (Unlicensed) look into the ability to set permissions for fix-version and priority in Jira 27 Jun 2019

Browser not supported