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

Hi, one major remark. I believe this is wrong assumption that REQ by „design” must be completed in one release. If feature is big and releases are more frequent it is impossible to deliver bigger chan

#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, Yesterday, the TSC agreed with my recommendation that RC1 was NOGO. Although a great deal of work has been done, and several projects have completed their release management tasks, several issue

#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, 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

#guilin #integration #test #requirements

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, 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

Team, Guilin M2/M3 is less than two weeks from now (Aug 6). So far, I've only noticed a few projects that have closed any of their release management tasks, which were published last week. Remember th

#guilin

Team, Today, the TSC approved the completion of Guilin M1. Guilin M2/3 is scheduled for August 6. Please let me know if you have any questions. David

#guilin

Note that I inadvertently generated issues for AAF. Those have now been closed. David

#guilin

Ok - done. I also added VNFRQTS. - D

#guilin

Eric, Thanks for that feedback! Let me discuss with your concerns with the CDS team and come back with a plan to make sure we’re being as transparent as possible. Thanks! Dan From: <onap-tsc@...

#guilin

Team, I just realized that I inadvertently left the project planning template off of the list of tasks for M1. This has now been corrected. My apologies for the oversight. David

#guilin

Team, I had an action item from the TSC to coordinate with Chaker to verify the arch review status of requirements and use cases on the Guilin requirements page. When I met with Chaker, we identified

#guilin