Topics, Notes, and Follow-Up Tasks
Backlog Issues | Notes / Status | Follow-up | ||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Release / Branching Strategy |
|
| ||||||||||||||||||||||||||||||||||||||||||||||||
Naming Standard | SDC and Modeling are using 1.1.0 - is this acceptable - should we just have one naming convention? Questions to be answered whenever the TSC votes to create a named release:
We can probably accommodate different names for (#1) and/or some delay to starting #2 as long as everyone has the same view a timeline. Is there isn’t a better way use tags, eg
| Topic for lessons learned at Santa Clara F2F? Gregory Glover
Touch base with OpenNFV / other Open Source projects? | ||||||||||||||||||||||||||||||||||||||||||||||||
Test Lab | Create for HEAT and OOM: Ticket
| |||||||||||||||||||||||||||||||||||||||||||||||||
New Projects | See: Doc Work Plan for Beijing (Release 2) |