Hi PTLs, M4 Code Freeze review for Beijing Release is coming and will be hold on March 29 at 7 am PDT during the weekly TSC Meeting. Please make it possible to join the bridge or send out a delegate. TSC may have questions on which we expect timely responses.
1. As usual, please make a copy and fill out the M4 template<https://wiki.onap.org/display/DW/Deliverable+for+Code+Freeze+Milestone+Checklist+Template>. I would appreciate if you could fill it out by COB on Tuesday, March 27. Early is even better so we have time to clarify items (if necessary). 2. At M1, the teams have made commitments in regards to Platform Maturity and Functional requirements. The commitments were all recorded in a central wiki page. As M4 Code freeze is coming, the community needs to understand where the teams stand in regards to these commitments and such the request is you update accordingly the column labelled "R4 result" for Platform Maturity<https://wiki.onap.org/display/DW/Beijing+Release+Platform+Maturity> (Level achieved 1-4) and Functional Requirements<https://wiki.onap.org/display/DW/Beijing+Functional+Requirements> (Yes/No answer). Please answer by the intent the team had to develop these commitments, not by the outcome of integration testing which we have not performed yet. I know we are not living in a perfect world, some defects will come out of the testing and collectively we will address them. The critical point is to create awareness in case some of these commitments would not be in the scope of Beijing Release. 3. The community will be also looking at: a. Code Coverage for each Java and Python repo in the scope of Beijing Release. 50% line code coverage is the target in Sonar<https://sonar.onap.org/projects?sort=name>. In case you are facing difficulty in seeing your code coverage in Sonar, please create a LF ticket and CC me. b. CSIT testing: check that all the CSIT pass in Jenkins<https://jenkins.onap.org/view/CSIT/>. c. CLM Nexus-IQ report: All critical (level 8-9) license issues addressed and all critical (level 7-10) security issue either fixed or properly documented in wiki by using template<https://wiki.onap.org/pages/viewpage.action?pageId=25435956>. These templates will be used as a reference point from your components Release Notes. d. The pending commits older than 36 hours<https://gerrit.onap.org/r/#/q/status:open+age:36h>. By pending we mean a commit on which no activity happened during the last 36 business hours. Back and forth reviews is seen as activity and does not count as pending. Skin in the game matter :). e. Keep the Risk you have identified in centralized table up-to-date<https://wiki.onap.org/display/DW/Beijing+Risks>. The world in changing fast. In case a risk will not become an issue, update its status to "Not occurred". In case a risk materialized and became an issue, update its status to "In-process". I will be attending ONS next week and will be glad to seat with you to address any questions you may have. For those who cannot make it to ONS, if needed let me know and I will open a Zoom meeting on first come first served. Let me know if you have any questions. Wish us all the best in making this reality. Thanks, Gildas [HuaweiLogowithName] Gildas Lanilis ONAP Release Manager Santa Clara CA, USA [email protected] Mobile: 1 415 238 6287
_______________________________________________ ONAP-TSC mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-tsc
