11-08-2017 Portal Platform Weekly Meeting
Agenda:
Finalize RC02 checklist before Nov 9
Go over JIRA list assigned for Beijing release
Discuss new features for Beijing release what planned for May 2018
Attendees:
Manoop Talasila, @Chris Lott, Lorraine Welch, @Weiting, @Leimeng Shi, @Sunder Tattavarada
Discussion Items:
Finalize the On-Board script for Amsterdam release - (Leimeng/Chris L) - Done
Email to LF team for Docker images release - done
Test the final docker images that are released - Leimeng and Kishore
Check with Marco - if the heat scripts need to be updated with release docker image tags? - Manoop
Documentation release notes needs to be approved by Greg - Leimeng
One last GREP scan and License scan before Amsterdam release - (Lorraine)
R2 planning, Leimeng will create US that defined in TDP -1802 feature.
Raise Sonar coverage to 50%
1802 Changes - (Sunder)
Pending JIRA items for Beijing
New UI changes?? - Bootstrap UI, Angular 4.0, Spring latest, Springboot
New UI changes
Grunt/Bower → Babel/Yarn upgrade to fix the depreciation issue and makes it easy to keep up with all the libraries to latest versions.
Design to upgrade Demo SDK app into Springboot app.
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.