Agenda:

  1. Finalize RC02 checklist before Nov 9
  2. Go over JIRA list assigned for Beijing release
  3. Discuss new features for Beijing release what planned for May 2018

Attendees:

Manoop Talasila, Chris Lott, Lorraine Welch, Wei-Ting Lo, Leimeng Shi, Sunder Tattavarada

Discussion Items:

  1. Finalize the On-Board script for Amsterdam release - (Leimeng/Chris L) - Done
  2. Email to LF team for Docker images release - done
  3. Test the final docker images that are released - Leimeng and Kishore
  4. Check with Marco - if the heat scripts need to be updated with release docker image tags? - Manoop
  5. Documentation release notes needs to be approved by Greg - Leimeng
  6. One last GREP scan and License scan before Amsterdam release - (Lorraine) 
  7. R2 planning, Leimeng will create US that defined in TDP -1802 feature.
    1. Raise Sonar coverage to 50%
    2. 1802 Changes - (Sunder)
    3. Pending JIRA items for Beijing
    4. New UI changes?? - Bootstrap UI, Angular 4.0, Spring latest, Springboot
  8. New UI changes
    1. Grunt/Bower → Babel/Yarn upgrade to fix the depreciation issue and makes it easy to keep up with all the libraries to latest versions.
    2. Design to upgrade Demo SDK app into Springboot app.
  9. Here are the release plan dates again for your reference:
  • 10/20 – branching out portal 1.3.0 (waiting on name change in URL) - done
  • 10/26 – last opportunity for critical bugs - done
  • 11/09 – sign-off for R1 (Waiting on documentation approval)


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.

  • No labels