Page History

...

Everyone should immediately begin following the model used by many other OSS communities and change your Zoom name to First-name FAMILY-NAME (company) – capitalization of family name here is intentional to help our global community.  
Example:  Hosty MCHOSTFACE (Fetzervalve)

WAITING ROOM ENABLED by default; HOST/CO-HOST will allow attendees following zoom naming convention.

Recording:

DCAE_Weekly_10212020.mp4

Attendees:

Host: Vijay Venkatesh Kumar  (AT&T)

Image Added

Discussion Topics:

• dcaegen2
• dcaegen2/deployments
• dcaegen2/platform/blueprints
• dcaegen2/services

As there are outstanding updates pending on above, these repo has not been branched yet (targeting next week except for dcaegen2 which will be done post RC0). Until then pls DO NOT merge any changes targeted POST Guilin on “master” branch for above repositories.

Couple of guidelines on approvals/merged on branched components

1. Guilin branch
1. Only critical bug fixes must be merged into guilin branches
2. patch version must be incremented for every bugfix
3. Self-release can be submitted into guilin branch
2. Guilin Maintenance  (schedule TBD)
1. Any change targeted for Guilin maintenance must go under “Guilin” branch only after release tagging is complete (around RC2)
2. Bug-fixes for Guilin-maintenance can go under “master” and later cherry-picked and released
3. Master branch
1. Post Guilin enhancement/optimization can be worked and approved but would suggest to hold merge until RC0.
2. Work with contributor to Cherry-pick any bug fix submitted under Guilin branch into master branches
3. Ensure master version is updated and do not conflict with guilin (typically we bump the minor version on master)

For following repository, the builds are dependent on artifacts being sourced from/pushed into nexus raw. Path submitted to reflect R8 path on master (Guilin will stay on R7); new updates >R7 can progress on these except for last two repo  (pending branching and merging patch submitted)

• dcaegen2/collectors/snmptrap
• dcaegen2/platform/plugins
• dcaegen2/utils
• dcaegen2/deployment
• dcaegen2/platform/blueprint

https://gerrit.onap.org/r/q/topic:%22R8-tag-branch%22+(status:open%20OR%20status:merged)

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 

Upcoming milestone RC0 - DCAEGEN2-2442

• Review Guilin packages (see below)

• dcaegen2

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

Couple of guidelines on approvals/merged on branched components

1. Guilin branch
1. Only critical bug fixes must be merged into guilin branches
2. patch version must be incremented for every bugfix
3. Self-release can be submitted into guilin branch
2. Guilin Maintenance  (schedule TBD)
1. Any change targeted for Guilin maintenance must go under “Guilin” branch only after release tagging is complete (around RC2)
2. Bug-fixes for Guilin-maintenance can go under “master” and later cherry-picked and released
3. Master branch
1. Post Guilin enhancement/optimization can be worked and approved but would suggest to hold merge until RC0.
2. Work with contributor to Cherry-pick any bug fix submitted under Guilin branch into master branches
3. Ensure master version is updated and do not conflict with guilin (typically we bump the minor version on master)

For following repository, the builds are dependent on artifacts being sourced from/pushed into nexus raw. Path submitted to reflect R8 path on master (Guilin will stay on R7); new updates >R7 can progress on these except for last two repo  (pending branching and merging patch submitted)

• dcaegen2/collectors/snmptrap
• dcaegen2/platform/plugins
• dcaegen2/utils
• dcaegen2/deployment
• dcaegen2/platform/blueprint

https://gerrit.onap.org/r/q/topic:%22R8-tag-branch%22+(status:open%20OR%20status:merged)

https://wiki.onap.org/display/DW/Moving+CSIT+to+project+repositories

• which docker images (names and versions) are under test*
• which docker images are required dependencies* for the test to run clear in all cases?
• Added in a README.md for each plan

Looking for volunteer to help with documentation 

Discuss status

• Bp-gen refactoring holding kafka support (HV-VES)
• RESTConf collector (CMPv2) - proposal not to implement for Guilin