Special note to [PTLs] - The following Actions are required by Friday @ 5pm Pacific time:
-Please take some time to review the topic planning page and add topics and/or questions to the list. https://wiki.onap.org/pages/viewpage.action?pageId=8232264 -Project team meetings will be cancelled unless you explicitly request to either keep them in place or add a project team item to the topic planning page. GENERAL INFORMATION FOR ALL COMMUNITY MEMBERS: - DATE: July 24, 25 & 26 - Start times all three days: UTC 12:00 PM / China 08:00 PM / Eastern 08:00 AM / Pacific 05:00 AM - Bridge Information: TBD - The IRC channel will be the primary means of communication during this event http://webchat.freenode.net/?channels=onap-meeting <http://webchat.freenode.net/?channels=onap-meeting> - We will be setting up a primary “moderated” Zoom conference sessions and two alternate “un-confrerence” sessions for breakouts. For the primary conference session we will be aggressively working to keep all lines muted due to a connection bug. Please make use of IRC for questions if at all possible. - Day 1 primary track agenda has been finalized below- (wiki to be updated soon) - Day 2 primary track will be use case focused - Day 3 is still TBD We are looking to the community to provide IRC note takers for these Welcome / Intro Architecture for Amsterdam and Beijing • Topic Leader: Chris Donley • Description: Present the latest architecture from the ARC subcommittee and begin project-by-project flow walk-throughs Validation of Dependency Graph • Topic Leader: Gildas Lanilis • Description: Gain agreement that all dependencies are accounted for and accurate Release Versioning • Topic Leader:Oliver Spatscheck • Description: Discuss 2 versioning proposals for Amsterdam 1. We try to keep the version numbers all in sync and in sync with the release number which will require “down versioning” some of the code with all the problems that will cause with dependencies and artifact caching. It will also be difficult to maintain as we are applying patches after the Amsterdam release is out (a patch to one component would trigger a version update to all other components). 2. We allow each repo to manage there own version number and then the Amsterdam release is just really a collection of artifacts with different version numbers properly tagged/referenced. Release Status, Release Process and Scrum Board Usage • Topic Leader: Gildas Lanilis • Description: This session will cover 3 main topics: 1. Where do we stand in regards to Amsterdam Release Planning 2. From a process perspective, what are the next milestones, and what is expected from each team 3. How do we provide adequate transparency across teams by using Scrum Board E2E Test Cases • Topic Leader: Helen Chen • Description: Deep dive on End-to-End Test Case considerations - Members of the community are responsible for reserving their own time slots in the alternate sessions. This is on a 1st come, 1st served basis, similar to what we did in Beijing. The wiki page HAS NOT been updated to include the two alternate tracks yet. This will be done within the next 24 hours. More info / updates will be provided as warranted. Best Regards, -kenny Kenny Paul, Technical Program Manager [email protected] 510.766.5945
_______________________________________________ ONAP-TSC mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-tsc
