The decision on M3 has been pushed out to Monday, March 1 at the PTL meeting. So, please continue to close your M3 issues. David

#honolulu

Requirements Owners, I have published the release management tasks for RC0. Alla - please review at the Requirements Subcommittee meeting. Note that RC0 is scheduled for March 11. Let me know if you h

#honolulu

Reminder... two days left.

#honolulu

Team, The tasks for Honolulu RC0 have been published to Jira. Please find the epic for your project from the list below. Note that RC0 is scheduled for Mar 11. Let me know if you have any questions. D

#honolulu

Team, I just realized that I did not publish a page to collect exceptions for Honolulu. Sorry for the oversight! I just created the page: https://wiki.onap.org/x/8DyLBQ Let me know if you have any que

#exception #honolulu

Team, Due to a conflict with the developer forum next week, the TSC agreed today to change the dates for the exceptions to be resolved, cited in my previous email, to Feb 9 and Feb 16, respectively. L

#honolulu

FYI - M1 exceptions have been closed. Let me know if you have any questions. David

#honolulu

Team, Today, the TSC agreed that the requirements for Honolulu M2 have not yet been met. The milestone status will be reviewed again on Monday, Jan 25. Please let me know if you have any questions. Da

#honolulu

Reminder... Honolulu M2 is scheduled tomorrow (Jan 21). If you have not completed your M1 or M2 tasks, please do so now. David

#honolulu

Team, I neglected to include the Honolulu Use Cases. Here they are: Epic: REQ-456 - CCVPN - Transport Slicing use case requirements for Honolulu release Release Management Tasks: REQ-530 REQ-531 Epic:

#honolulu

Team, The Honolulu M2 tasks have been published. Note that you may notice some changes from past releases. This is in keeping with the new release process. Find the relman epic for your project from t

#honolulu

Team, I just published an additional task for M1, based on my meeting with Krzysztof earlier this week. Let me know if you have any questions. Just a reminder that M1 is scheduled for Jan 11. David

#honolulu

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

Team, I just added a comment to Guilin REQ issues whose status is NOT 'Done'. Since we are ending the Guilin release this week, these issues need to be updated as 'Done'. I included the steps in Jira,

#honolulu

Team, Following several meetings over the last two weeks to clarify the terminology and milestone tasks for the new release process, we have a new schedule for your review. Thanks to @Krzysztof Opasia

#honolulu

Dear Honolulu Requirement Owners, As previous requested - https://lists.onap.org/g/onap-tsc/message/7135 Please do not forget to … Define the Global Requirements and create the epic in JIRA and associ

#honolulu

Team, As a reminder, your Honolulu release requirements are due today (Oct 16). https://wiki.onap.org/x/h8ALBQ David

#honolulu

Team, On today's TSC call, I shared the Honolulu requirements page. Unfortunately, I realized later that the permissions for the jira filters that are embedded in the page were still set to private. T

#honolulu