Hi All,
This is regarding the action items
2,f<http://ircbot.wl.linuxfoundation.org/meetings/onap-meeting/2017/onap-meeting.2017-10-05-13.52.html>
on Thursday, Oct 5 2017 TSC weekly meeting.
I have been able to upload in wiki the excel sheet that I used to monitor M4
progress at https://wiki.onap.org/display/DW/M4+Status . It provides all the
details on what is left to do for the teams. Looks like I am the only one who
can edit the file.
I also maintain the overall master Amsterdam Release Status at
https://wiki.onap.org/display/DW/Release+Status
Since the TSC meeting, CCSDK (Gating project) has reached the 30% code coverage
on ccsdk-sli-northbound repo and thus made the M4 criteria.
AAF (Non-gating project) also reported the fact the team had reached to 30%
code coverage. However, AAF did not meet the Oct 2 timeline and thus won't be
part of Amsterdam release (refer to attached information)
Thanks,
Gildas
[HuaweiLogowithName]
Gildas Lanilis
ONAP Release Manager
Santa Clara CA, USA
[email protected]
Mobile: 1 415 238 6287
--- Begin Message ---
Dear PTLs,
On behalf of the TSC, I wanted to thank you for your leadership and drive to
get us to the Amsterdam release on Nov 16th. You and your teams are incredible
role models of how a community is harmonizing towards a common goal.
As we discussed at the Paris meeting, we have to make some hard decisions to
get to the Amsterdam release on November 16th. The TSC, with feedback from
Gildas and Helen, have decided on the following
All projects should at least pass the M4 milestone and a min of 30% unit
coverage by next Monday EOB (PST)
Non-gating projects that do not meet this timeline will be removed from the
formal release.
Gating projects will need to provide a date of when they expect to reach this
milestone.
Gildas will collect all info and share with the community Monday night (PST)
thanks!
Mazin
--- End Message ---
_______________________________________________
ONAP-TSC mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-tsc
