Page Comparison

Honolulu Reference  (Important Links)

• Honolulu Release Requirements
• Honolulu Impact View per Component
• Honolulu Integration Blocking Points
• Release planning 
• Release EPIC's 
  • M1 - DCAEGEN2-2552
  • M2 - DCAEGEN2-2561
  • M3 - DCAEGEN2-2601
  • RC0 - DCAEGEN2-2643
• CSIT - https://jenkins.onap.org/view/CSIT/
• Honolulu Exceptions for DCAE (TBD)

Honolulu Release Key Updates

See table below

(3 changes from last week)

• DFC
• Bootstrap
• Cloudify Manager

• With exception of dcaegen2 (documentation repo), all other DCAE repository has been branched.
• Documentation branching will be done towards end of RC1
• CI jobs for Honolulu setup

Code submission Guidelines

Honolulu

1. Only bug-fixes (critical/high) or integration blockers must be allowed for H release scope
1. Ensure “patch” versions are bumped for bug-fixes
2. All container release yaml to be submitted under “master” branch - job reference can point to Honolulu specific release job (within the yaml)
3. Change should be cherrypicked accordingly (master-honolulu)
4. Container version update
1. For all bootstrapped components
   1. version bump to be submitted directly under OOM (both master and Honolulu branch)
   2. Blueprint updates to be submitted on both master/honolulu – but no bootstrap release required.
   3. Note: Only in scenarios where application blueprint/configuration change beyond version is necessary – bootstrap release will be required.
2. For all NON-bootstrapped components
   1. Blueprint updates to be submitted on both master/honolulu for version revision– but no bootstrap release required here also.
   2. Note: Only in scenarios where application blueprint/configuration change beyond version is necessary – bootstrap release will be required.
   3. Update documentation to reflect the version override required for MS deployment
3. ** If there are multiple blueprint updates made for H release – then we can assess if we need to consolidate/release bootstrap during RC phase.
5. All documentation update for H release to be submitted on “master” until branching is done (around RC1)

Istanbul

1. Hold off merge on documentation updates being submitted for post H release; you can review and comment accordingly or mark WIP
2. Once https://gerrit.onap.org/r/q/topic:%22R9-tag-branch%22+(status:open%20OR%20status:merged) are all merged, new changes for instabul can be reviewed/merged.

• Ensure “minor” versions are bumped (and not conflicting with release branch)

Day-light saving begins this weekend in US

DCAE meeting will remain at UTC 14:30