Hi, so as long as it goes about the new release process I share Lukasz point of view. Key differences between old release process and new one is: 1) Split technical discussion on proposed change and t

#guilin #honolulu

I second David opinion. Mira description should include what is planned for specific Release only. Best regards, Alla Sent from Nine

#guilin #honolulu

Team, I've gotten some questions about continuing a requirement from one release to the next. So, for example, from Guilin to Honolulu. In order to track history, we decided that it would be better to

#guilin #honolulu

Hi, As I am working on the Guilin Documentation, I would like to know, what is the decision for handling the projects in “Maintenance” state. CLI APPC AAI/ESR AAI/Sparky MUSIC Logging Should these pro

#guilin

Team, The release management tasks for RC2 have been published. Please find the epic Jira issue for your project from the list below. Note that RC2 is scheduled for Nov 19, coincident with sign off. D

#guilin

Team, Just a reminder that RC1 is scheduled for tomorrow, Nov 5. The milestone status shows that we still have ~40% of the release management issues that are not yet closed. Let me know if you have an

#guilin

REMINDER... Please update the following fields for your integration test issues before the TSC meeting tomorrow: Integration Test Status Integration Test Time to Complete If your test issue is blocked

#integration #test #guilin

Team, The release management tasks for RC1 have been published. Please find the epic Jira issue for your project from the list below. The schedule for RC1 is now Nov 5. Let me know if you have any que

#guilin

Team, Today, the ONAP TSC approved the Guilin RC0 milestone, with the provision that the "war room" continue work on resolving ongoing SO and OOM related issues. In addition, the TSC approved a change

#guilin

Good evening Marcin, We are focusing on the test plan associated to the Guilin use cases and functional requirements. Nevertheless we also expect that regression tests are performed if requirements fr

#guilin #integration #test #requirements

Requirement / Use Case Owners and Integration Test Leads, As you know, we track integration test plans, and the progress of Use Cases and Requirements through the end of the release process, by tracki

#requirements #guilin #integration #test

Correcting mailing list error.

#integration #guilin

Team, In reviewing the milestone status for RC0/Guilin, I see that nearly half of our participating projects have not yet started on their milestone tasks. Note that we only have two weeks until the s

#guilin

Team, The release management Jira issues for RC0 have been published. Please find the Jira epic for your project from the list below. Let me know if you have any questions. AAI-3187 DCAEGEN2-2442 CCSD

#guilin

Team, Today, the TSC approved Guilin M4 with some exceptions. Please see the minutes for additional details. Please be aware that our next milestone, Guilin RC0, is at risk due to ongoing issues at th

#guilin

Team, As a reminder, M4 is just one week away (Sept 10). Please complete your release management tasks as soon as possible. Let me know if you have any blocking issues. David

#guilin

Team, The M4 relman Jira issues have been published. Find the Jira ID for your project below. Let me know if you have any questions. David AAI-3108 DCAEGEN2-2389 CCSDK-2650 CLI-302 HOLMES-346 DMAAP-14

#guilin

Team, I'm pleased to report that today (Aug 13) the TSC approved Guilin M2/3 with conditions. See the minutes for additional details. Guilin M4 is scheduled for September 10. Please let me know if you

#guilin

Reminder... M2/3 is scheduled this Thursday, Aug 6.

#guilin

Team, If you haven't already done so, please enter the scorecard for your requirement or use case for Guilin M1. If your requirement has been de-scoped, or your requirement is PoC, this is not necessa

#guilin