Agenda:

1. Go over JIRA list assigned for Beijing release
2. Discuss new features for Beijing release what planned for May 2018

Attendees:

Manoop Talasila, Chris Lott, Lorraine Welch, Weiting, Leimeng Shi, Sunder Tattavarada, MULLICK, GARIMA

Discussion Items:

1. Sonar coverage to 50%, assigned to Hima.
2. AAF-PORTAL roles auto synch test (need URL from Sai) - Leimeng and Hima
3. Follow up email to partners for SDK package update initiated by Sunder T. (remove ECOMP) - Leimeng
4. Beijing Release Planning:
1. M0 - dev kick-off, Nov 16
2. M1 - planning Jan 16
3. M2 -  functionality freeze Feb 15
4. M3 - API freeze Mar 1
5. M4 - code freeze Apr 5

NOTE: Decision from TSC regarding the next maintenance releases - 

The proposal, create AMS branch on Nov. 10th, create an AMS Maint release on Jan. 18th; may only have one maintenance release, depending on bugs reported.  Regardless, support for AMS would be completed at the introduction of Beijing. Does the TSC approve the Option 3 branching proposal recommendations for having Amsterdam service releases one month apart with the first release targeted for Jan 17, 2017, terminating with the Beijing release? Yes.