...
| Agenda | Minutes (Draft to be updated during call) | Slides | ||||||||||||||||||||||||||||
High Priority Bugs | High priority defects :
| |||||||||||||||||||||||||||||
| Open review | ||||||||||||||||||||||||||||||
| Jakarta Release timeplan |
M1 (Global requirement freeze) scheduled for 2nd December
Tasks for M1:
M1 postponed by 1 week from 2nd to 9th Dec. Other milestones unaffected We should plan to release more often in Jakarta to move towards a more CI way of working.
M1 approved by TSC
M2 milestone scheduled for 27th January
First delivery for Jakarta (1.10.0) built and submitted to OOM (https://gerrit.onap.org/r/c/oom/+/126602). Content can be seen here: https://docs.onap.org/projects/onap-sdc/en/latest/release-notes.html#version-1-10-0 Still in review in OOM 1.10.1 built and submitted to OOM (https://gerrit.onap.org/r/c/oom/+/127003) M2 passed last Thursday 3rd Feb. Next milestone is M3 on 3rd March | |||||||||||||||||||||||||||||
| Jakarta Impacts | Portal is in unmaintained state in Istanbul and is proposed to be removed in Jakarta, need to consider how user authentication for SDC UI to be performed if portal is removed
Proposed new global requirement: REQ-441 ONAP application log to stdout and stderr Proposed new best practice: Standardized Logging Fields, see Jakarta Best Practice Proposal for Standardized Logging Fields
Previous best practice
Proposed impact for Jakarta:
| |||||||||||||||||||||||||||||
| Q&A |
...