Page Comparison

Table of Contents

...

Time (est)

Topics

Requester/Assignee

Notes/Links

START RECORDING

PARTICIPANT LIST

DST impacts - PTL 2020-10-26

1

Project Status & General updates

Vijay Kumar

Current Open issues

Memory leak on VESCollector (Jira to be created)

Jira Legacy

server	System Jira
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues	20
jqlQuery	filter=12333
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176

Open from last meeting

DCAEGEN2-2463: DCAE multisite-init-container Docker image build fails - Move to H release
DCAEGEN2-2455: DCAE dockers contain GPLv3 - Move to H release

Note: Bootstrap revision/release to be consolidated (btw now and RC1)

First patch merged must include version bump
Subsequent patches can be merged without version bump as long as not release
Selfrelease yaml snapshot must include latest snapshot

Guilin Reference

Guilin priorities (TSC) - TSC presentation
Guilin Release Requirements
Release Planning: Guilin
RC1 - DCAEGEN2-2496
- RC0 - DCAEGEN2-2442 (DONE)
- M4 - DCAEGEN2-2389 (DONE)
- M2/M3 - DCAEGEN2-2354 (DONE)
- M1 - DCAEGEN2-2299 (DONE)
DCAE R7 M1 Release Planning
DCAE ARC review
- ARC DCAE Component Description - Guilin (R7) Release (Copy)
- DCAE R7 - M3 Architecture Review
Project Maturity Review for DCAE
CSIT - https://jenkins.onap.org/view/CSIT/
Guilin Exception Request for DCAE
Security Vulnerability -
Jira Legacy
server System Jira
serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
key DCAEGEN2-2242
Pairwise Test - DCAE Pair Wise Testing for Guilin Release

Vijay Kumar

Upcoming milestone RC0 - DCAEGEN2-2442

Review Guilin packages (see below)

2

DCAE Outstanding Jira & MED priority bugs (Guilin)

Vijay Kumar

Jira Legacy

server	System Jira
jqlQuery	filter=12436
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176

3

Review Guilin Branching

Branched majority of DCAE repositories for Guilin release with corresponding CI jobs in place – with the exception of following repositories

dcaegen2

Branching for dcaegen2 (documentation) will be done toward end of RC1. Until then DO NOT merge any doc changes targeted POST Guilin on “master” branch for dcaegen2 repositories.

Couple of guidelines on approvals/merged on branched components

Guilin branch

Only critical bug fixes must be merged into guilin branches
patch version must be incremented for every bugfix
Self-release can be submitted into guilin branch

Guilin Maintenance (schedule TBD)

Any change targeted for Guilin maintenance must go under “Guilin” branch only after release tagging is complete (around RC2)
Bug-fixes for Guilin-maintenance can go under “master” and later cherry-picked and released

Master branch

Post Guilin enhancement/optimization can be worked and approved but would suggest to hold merge until RC0.
Work with contributor to Cherry-pick any bug fix submitted under Guilin branch into master branches
Ensure master version is updated and do not conflict with guilin (typically we bump the minor version on master)

Honolulu Focus

Vijay Kumar