Team, Thanks for your efforts. All of the affected projects have now updated their release notes for the El Alto and the Frankfurt maintenance releases. David

#elalto #frankfurt #releasenotes

Hi Andreas, Krzysztof, You will notice the 6.0.1-ONAP tag only on the projects that participated on the maintenance release: policy policy/pdp ccsdk/cds testsuite sdc sdnc so We probably need to bring

#frankfurt #maintenance #release

Team, All issues have been resolved for the maintenance release. Cross-testing results are positive, so we are prepared to move forward with the release. The following projects are affected: AAF CCSDK

#frankfurt #maintenance

+Sofia Wallin Sofia - note the date of July 10 for release notes for El Alto and Frankfurt release notes. David

#elalto #frankfurt

Team, I wanted to update you on the status of the Frankfurt release. Last week, the TSC agreed to combine the RC2 and Sign-Off milestones. This week, on Monday and again on Thursday, the TSC reviewed

#frankfurt

Reminder.. We will have an extraordinary TSC meeting at 2 p.m. UTC (7 a.m. Pacific) on May 26 to consider the status of Frankfurt RC2. See the TSC calendar for the logistics. We will also have our usu

#frankfurt

Team, Based on the discussion with Steve Winslow earlier this week, the proposed additional task for RC2 is withdrawn and you may disregard my email at the start of this thread. David

#frankfurt

PTLs, Please complete your release requirements for RC2 by next Tuesday. Let me know if you have any questions. David

#frankfurt

Just realized that I used the wrong link for AAF-1127. Here's the correct link: https://jira.onap.org/browse/AAF-1127 David

#frankfurt

Morgan, Thanks for the summary. My plan is to recommend to the TSC that they approve RC1, with the exception of AAF-1127. I appreciate the effort necessary to reinstall RC1; however, I think that we n

#frankfurt

Team, RC1 has been delayed one more day to 5 p.m. (Pacific) on Friday, May 8. The remainder of the schedule is unaffected. Let me know if you have any questions. David

#frankfurt

Hello, I do acknowledge that OOM has still (36 in last count) open tickets related to Frankfurt. But in my opinion, having still M4 issues is more improtantt so my goal is first to solve everything th

#frankfurt

Team, The Frankfurt RC1 milestone has been delayed to May 7, based on feedback from the integration team and the milestone status. The updated schedule may be found here. Let me know if you have any q

#frankfurt

Team, In order to make sure that you see all of the JIRA issues that are assigned to your project for the Frankfurt release that have not been closed, please use the following JIRA search query, so th

#frankfurt

Congratulations Team ! Great accomplishment ! I look forward to seeing your progress on the E2E Testing activities 😉 – Keep going ! Best regards Catherine

#release #frankfurt

Team, I have now also published the RC2 issues, as well as completed the customized issues for both RC1 and RC2, so all projects should have all of their issues for both milestones. If you believe tha

#frankfurt #jira

Team, Per our discussion in today's PTL meeting, I have published the RC1 JIRA issues. Please find the epic for your project in the list below. Note that I'm still working on the customization for som

#frankfurt #jira

Hi Jess, I have tried the docker release job today and observed that the tag is automatically set in the git repo. Thank you. Regards Kanagaraj Manickam Lead Architect Cloudfiy Networking OSDT Huawei

#release #frankfurt

Team, During our PTL meeting on Monday (Mar 30), we had a discussion to clarify some of the tasks assigned to RC0. We did not reach a conclusion on "verify project release tag," so I took an action it

#frankfurt #release

Team, Today, I published the JIRA issues for Frankfurt milestone RC0. See the list below for the JIRA epic for your project. In addition, per direction from the TSC, I moved the code coverage task for

#frankfurt #rc0 #release