...
Duration | Agenda Item | Requested by | Notes / Links | ||||||
---|---|---|---|---|---|---|---|---|---|
START RECORDING | |||||||||
Release Management: review of Casablanca Maintenance Release plan, including timeline, scope and processes. |
Notes: M1 maintenance Release on Dec 10 to refine scope. AI: Yang Xu to follow up with CCVPN Use case on their engagement for Integration testing and lab availability. AI: Gildas Lanilis Gmail Ticket LF to maintain CLM job on Casablanca Branch | ||||||||
Java Code Style has been decided, but what about other languages (Javascript). In addition, there are other non-code files: (XML, JSON, YAML) that could also use a style editor. Also, the oparent checkstyle is broken in 3 ways: 1) Doesn't work in Eclipse 2) src/main/java does not point to the right place: ${project.build.sourceDirectory}/src/main/java? appends an extra src/main/java to the end. 3) Parsing error in the oparent checkstyle.xml </module>? <module name="NeedBraces"/>? <module name="LeftCurly">?- <property name="maxLineLength" value="120"/>?+ <!--property name="maxLineLength" value="120"/-->? </module> | Pamela Dragosh | Pamela Dragosh is leading the initiative along with Seshu Kumar Mudiganti and Michael O'Brien. Anyone else is welcomed to join the initiative. Low priority initiative to try to come up with a common way for formatting and check style accross ONAP (this facilitates code review). Using Google Code Style and tools as the foundation |
Notes
Action items
- Yang Xu to follow up with CCVPN Use Case on their engagement for Integration testing and lab availability.
- Gildas Lanilis Gmail Ticket LF to maintain CLM job on Casablanca Branch. LF Ticket [ONAP Helpdesk #64966].
- Pamela Dragosh to lead the Code Style Initiative and update PTLs on progress.
- Meeting Helpdesk #64961 request sent for kickoff meeting on at 10:30am EST (3:30pm UTC) - FYI Seshu Kumar Mudiganti and Michael O'Brien this is really the only time that does not conflict with PTL or TSC meeting.
...