zoom bridge: https://zoom.us/j/283628617
Duration 60 minutes
| Duration | Agenda Item | Requested by | Notes / Links |
|---|---|---|---|
| START RECORDING | |||
Emergency Maintenance Release - Tag: 3.0.2
| TSC-120 - Getting issue details... STATUS | ||
| M3 follow up topics | Former user (Deleted) | Use case YELLOW - blocking defects? Alla.Goldner Component & Global Optimizations Eric Debeau S3P djhunt Additional functional tests OOM Morgan Richomme xNF communication security enhancements Linda Horn Amy Zwarico Locale/Internationalization Tao Shen | |
M4 Preparation
| |||
| 10min | Documentation process overview Hack a thon days | Process overview, PTL 2019-01-21 | |
| 2min | WindRiver Clean-Up checkpoint | Yang Xu | Jim sent the delete list to WR on 2019-03-19 - Cleanup complete 2019-03-20 Reduced: 40 vCPUs, .9TB RAM, 7TB Disk |
| 5min | Consistent Java code style using maven plugins | Regarding instructions under Setting Up Your Development Environment Instead of starting with Google style and Setting Up Your Development Environment Suggest using Setting Up Your Development Environment as the ONAP style formatter file is committed to the repo In AAI-2198 - Getting issue details... STATUS two maven plugins were trialled in AAI using the formatter XML file above, as intended to pass "onap-java-style" checkstyle audit. Plugins can do batch re-formatting of Java code in the repository and run the audit, e.g.: mvn formatter:format spotless:apply process-sources Suggest that the formatter file and plugin config be adopted into oparent for all to share. Otherwise individual projects can copy the configuration and adopt it for their own local usage as per Setting Up Your Development Environment | |
| 5min | Security related defects needing immediate attention | Amy Zwarico | JDWP, |