+++ /dev/null
-Milestone Readouts
-==================
-
-Milestone Status
-----------------
-
-.. toctree::
- :glob:
- :maxdepth: 1
-
- milestone-readouts/status/*
-
-M0: Declare Intent
-------------------
-
-.. toctree::
- :glob:
- :maxdepth: 1
-
- milestone-readouts/m0/*
-
-M1: Final Release Plan
-----------------------
-
-.. toctree::
- :glob:
- :maxdepth: 1
-
- milestone-readouts/m1/*
-
-M2: Functionality Freeze
-------------------------
-
-.. toctree::
- :glob:
- :maxdepth: 1
-
- milestone-readouts/m2/*
-
-M3: API Freeze
---------------
-
-.. toctree::
- :glob:
- :maxdepth: 1
-
- milestone-readouts/m3/*
-
-M4: Code Freeze
----------------
-
-.. toctree::
- :glob:
- :maxdepth: 1
-
- milestone-readouts/m4/*
-
-RCX: Release Candidate Testing
-------------------------------
-
-.. toctree::
- :glob:
- :maxdepth: 1
-
- milestone-readouts/rcx/*
+++ /dev/null
-===
-AAA
-===
-
-1. The Authentication, Authorization and Accounting (AAA) project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 0
-
-3. Project Category: Kernel
-
-4. Project Labels: Authentication, Authorization and Accounting, AAA
-
-5. Project PTL: Ryan Goulding, ryandgoulding@gmail.com, rgoulding
-
-6. Do you confirm that the list of Project Committers is updated and accurate? No, working on this.
+++ /dev/null
-====
-ALTO
-====
-
-1. The ALTO project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 2
-
-3. Project Category: Service
-
-4. Project Labels: ALTO, network abstraction, network optimization
-
-5. Project PTL: Kai Gao, gaok12@mails.tsinghua.edu.cn, emiapwil
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-===========
-BGP PCEP LS
-===========
-
-1. The BGP PCEP project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 1
-
-3. Project Category: Protocol
-
-4. Project Labels: bgp, bmp, pcep, bgp pcep ls
-
-5. Project PTL: Claudio D. Gasparini, claudio.gasparini@pantheon.tech, cgasparini
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-====
-BIER
-====
-
-1. The Bit Indexed Explicit Replication (BIER) project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 2
-
-3. Project Category: Service
-
-4. Project Labels: BIER, multicast
-
-5. Project PTL: Quan Xiong, xiong.quan@zte.com.cn, xiong.quan
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-===
-COE
-===
-
-1. The Container Orchestration Engine (COE) project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 2
-
-3. Project Category: Application
-
-4. Project Labels: Kubernetes integration, Kuryr, Containers
-
-5. Project PTL: Prem Sankar G, prem.sankar.g@ericsson.com, premsankar
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
-
-
-
-
-
+++ /dev/null
-==========
-Controller
-==========
-
-1. The Controller project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 0
-
-3. Project Category: Kernel
-
-4. Project Labels: Controller
-
-5. Project PTL: Tom Pantelis, tompantelis@gmail.com, tpanteli
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
\ No newline at end of file
+++ /dev/null
-======
-DAEXIM
-======
-
-1. The Data Export/Import (daexim) project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 2
-
-3. Project Category: Application
-
-4. Project Labels: Data Export Import, daexim
-
-5. Project PTL: Shaleen Saxena, shaleen.external@gmail.com, ssaxena
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-====
-DLUX
-====
-
-1. The DLUX project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 1
-
-3. Project Category: Application
-
-4. Project Labels: ui, gui, angular, javascript, frontend
-
-5. Project PTL: Daniel Malachovsky, dmalacho@cisco.com, dmalachovsky
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-=================
-DLUX Applications
-=================
-
-1. The DLUX Applications project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 1
-
-3. Project Category: Application
-
-4. Project Labels: ui, gui, angular, javascript, frontend
-
-5. Project PTL: Daniel Malachovsky, dmalacho@cisco.com, dmalachovsky
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
\ No newline at end of file
+++ /dev/null
-====
-EMAN
-====
-
-1. The Energy Management Plugin (EMAN) project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 2
-
-3. Project Category: Application
-
-4. Project Labels: energy management
-
-5. Project PTL: Frank Sandoval, francisrsandoval@gmail.com, francisrsandoval
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
\ No newline at end of file
+++ /dev/null
-====
-FaaS
-====
-
-1. The Faas project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 2
-
-3. Project Category: Application
-
-4. Project Labels: Fabric, Logic Network Service
-
-5. Project PTL: Xingjun Chu, Xingjun.Chu@huawei.com, xingjun
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-======
-Genius
-======
-
-1. The Genius project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 1
-
-3. Project Category: Protocol
-
-4. Project Labels: Network Interfaces Utilities Services
-
-5. Project PTL: Vivek Srivastava, vivek.v.srivastava@ericsson.com, vivek.v.srivastava
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-==================
-Group Based Policy
-==================
-
-1. The Group Based Policy project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 2
-
-3. Project Category: Application
-
-4. Project Labels: groupbasedpolicy, gbp
-
-5. Project PTL: Michal Cmarada, mcmarada@cisco.com, michal-cmarada
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-=============
-Honeycomb/VBD
-=============
-
-1. The Honeycomb/VBD project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 2
-
-3. Project Category: Application
-
-4. Project Labels: honeycomb/vbd, vbd
-
-5. Project PTL: Michal Cmarada, mcmarada@cisco.com, michal-cmarada
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-==========
-Infrautils
-==========
-
-1. The Infrautils project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 0
-
-3. Project Category: Kernel
-
-4. Project Labels: infrastructure, utility
-
-5. Project PTL: Michael Vorburger, vorburger@redhat.com, vorburger
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-========================
-Integration/Distribution
-========================
-
-1. The Integration/Distribution project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 2
-
-3. Project Category: Support
-
-4. Project Labels: distribution, karaf
-
-5. Project PTL: Vratko Polak, vrpolak@cisco.com
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-========
-JSON-RPC
-========
-
-1. The JSON-RPC project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 2
-
-3. Project Category: Application
-
-4. Project Labels: json-rpc, jsonrpc
-
-5. Project PTL: Anton Ivanov, anton.ivanov@kot-begemot.co.uk, aivanov
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-=========
-L2 Switch
-=========
-
-1. The L2 Switch project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 1
-
-3. Project Category: Services
-
-4. Project Labels: hosttracker, arphandler, packethandler, mac learning, openflow
-
-5. Project PTL: Sai MarapaReddy, sai.marapareddy@gmail.com, sai_marapareddy
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-=================
-LISP Flow Mapping
-=================
-
-1. The LISP Flow Mapping project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 1
-
-3. Project Category: Protocol
-
-4. Project Labels: LISP, mapping service, overlay control pane, VXLAN-GPE
-
-5. Project PTL: Vina Ermagan, vermagan@cisco.com, vina_ermagan
-
-6. Do you confirm that the list of Project Committers is updated and accurate? No
+++ /dev/null
-======
-MD-SAL
-======
-
-1. The MD-SAL project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 0
-
-3. Project Category: Kernel
-
-4. Project Labels: mdsal
-
-5. Project PTL: Robert Varga, nite@hq.sk, rovarga
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-====
-NEMO
-====
-
-1. The NEMO project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 2
-
-3. Project Category: Application
-
-4. Project Labels: network modeling
-
-5. Project PTL: Tianran Zhou, zhoutianran@huawei.com, tianran
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-=======
-NETCONF
-=======
-
-1. The NETCONF project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 0
-
-3. Project Category: Kernel
-
-4. Project Labels: netconf, restconf
-
-5. Project PTL: Tomas Cere, tcere@cisco.com, tcere
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-=======
-NetVirt
-=======
-
-1. The NetVirt project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 2
-
-3. Project Category: Application
-
-4. Project Labels: network virtualization, openstack
-
-5. Project PTL: Sam Hague, shague@redhat.com, shague
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-==================
-Neutron Northbound
-==================
-
-1. The Neutron Northbound project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 1
-
-3. Project Category: Application
-
-4. Project Labels: openstack, neutron, networking-odl, northbound, network virtualization
-
-5. Project PTL: Isaku Yamahata, isaku.yamahata@gmail.com, yamahata
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-===
-NIC
-===
-
-1. The NIC project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 2
-
-3. Project Category: Application
-
-4. Project Labels: network intent composition
-
-5. Project PTL: Yrineu Rodrigues, yrineu.rodrigues@serro.com, yrineu_rodrigues
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-==========
-OCP plugin
-==========
-
-1. The OCP plugin project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 1
-
-3. Project Category: Protocol
-
-4. Project Labels: OCP plugin, OCP protocol library
-
-5. Project PTL: Chinning Lai, marko.lai@gmail.com, Chinning
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-==========
-ODL Parent
-==========
-
-1. The ODL Parent project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 0
-
-3. Project Category: Kernel
-
-4. Project Labels: parent POMs, SingleFeatureTest, Karaf integration
-
-5. Project PTL: Stephen Kitt, skitt@redhat.com, skitt
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-==========
-OF-CONFIG
-==========
-
-1. The OF-CONFIG project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 1
-
-3. Project Category: Protocol
-
-4. Project Labels: network modeling, Southbound Plugin
-
-5. Project PTL: Wei Meng, meng.wei2@zte.com.cn, valley
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-===============
-OpenFlow Plugin
-===============
-
-1. The OpenFlow Plugin project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 1
-
-3. Project Category: Protocol
-
-4. Project Labels: OpenFlow Plugin
-
-5. Project PTL: Abhijit Kumbhare, abhijitkoss@gmail.com, abhijitkumbhare
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-======
-OpFlex
-======
-
-1. The OpFlex project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 2
-
-3. Project Category: Application
-
-4. Project Labels: virtual networking
-
-5. Project PTL: Rob Adams, readams@readams.net, readams
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-=====
-OVSDB
-=====
-
-1. The OVSDB project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 1
-
-3. Project Category: Protocol
-
-4. Project Labels: OVSDB Southbound Plugin, OVSDB Hardware, vTep Plugin
-
-5. Project PTL: Anil Vishnoi, vishnoianil@gmail.com, vishnoianil
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-=========
-P4 Plugin
-=========
-
-1. The P4 Plugin project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 1
-
-3. Project Category: Protocol
-
-4. Project Labels: P4, P4Runtime, gRPC
-
-5. Project PTL: Ding Rui, ding.rui@zte.com.cn, ding.rui
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-===========
-PacketCable
-===========
-
-1. The Packetcable project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 2
-
-3. Project Category: Application
-
-4. Project Labels: cable telephony provisioning, COPS, CMTS
-
-5. Project PTL: Steve Pisarski, s.pisarski@cablelabs.com, spisarski
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-=========================
-Service Function Chaining
-=========================
-
-1. The SFC project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 2
-
-3. Project Category: Application
-
-4. Project Labels: Service Function Chaining, SFC
-
-5. Project PTL: Brady Johnson, bjohnson@inocybe.com, bjohnson
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-====
-SNMP
-====
-
-1. The SNMP project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 1
-
-3. Project Category: Protocol
-
-4. Project Labels: SNMP
-
-5. Project PTL: Ryan Goulding, ryandgoulding@gmail.com, rgoulding
-
-6. Do you confirm that the list of Project Committers is updated and accurate? No, working on this.
+++ /dev/null
-========
-SNMP4SDN
-========
-
-1. The SNMP4SDN project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 1
-
-3. Project Category: Protocol
-
-4. Project Labels: southbound plugin, commodify Ethernet switch, by SNMP
-
-5. Project PTL: Christine Hsieh, ylhsieh@itri.org.tw,ChristineH
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-===
-SXP
-===
-
-1. The SXP project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 1
-
-3. Project Category: Application
-
-4. Project Labels: SXP
-
-5. Project PTL: Michal Rehak, mirehak@cisco.com, michal_rehak
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-====
-TSDR
-====
-
-1. The TSDR project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 2
-
-3. Project Category: Application
-
-4. Project Labels: Time Series Data Repository
-
-5. Project PTL: YuLing Chen, yulingchen54@gmail.com, yulingchen
-
-6. Do you confirm that the list of Project Committers is updated and accurate? No, being updated.
+++ /dev/null
-======
-Unimgr
-======
-
-1. The Unimgr project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 2
-
-3. Project Category: Application
-
-4. Project Labels: MEF, Eline, netconf, T-API, connectivity services
-
-5. Project PTL: Donald Hunter, donaldh@cisco.com, donaldh
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-===
-USC
-===
-
-1. The USC project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 1
-
-3. Project Category: Protocol
-
-4. Project Labels: unified secure channel
-
-5. Project PTL: An Ho, an.ho@huawei.com, anipbu
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-===
-VTN
-===
-
-1. The VTN project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 2
-
-3. Project Category: Application
-
-4. Project Labels: vtn, virtual tenant network
-
-5. Project PTL: Hideyuki Tai, h-tai@cd.jp.nec.com, hideyuki
-
-6. Do you confirm that the list of Project Committers is updated and accurate? Yes
+++ /dev/null
-==========
-YANG Tools
-==========
-
-1. The YANG Tools project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: Offset 0
-
-3. Project Category: Kernel
-
-4. Project Labels: YANG
-
-5. Project PTL: Robert Varga, nite@hq.sk, rovarga
-
-6. Do you confirm that the list of Project Committers is updated and accurate? No
-
- - pending cleanup of committers who have left the ODL community
+++ /dev/null
-============
-Project Name
-============
-
-1. The <Project Name> project formally joins the OpenDaylight Oxygen
- Simultaneous Release and agrees to the activities and timeline documented on
- the Oxygen Release Plan Page:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
-
-2. Project Offset: (Offset 0/Offset 1/Offset 2)
-
-3. Project Category: (Kernel/Protocol/Services/Application/Support)
-
-4. Project Labels: (List keywords and tags that fit the description of your
- project comma separated)
-
-5. Project PTL:
-
- - name
- - email
- - IRC handle
-
-6. Do you confirm that the list of Project Committers is updated and accurate?
- (Yes/No)
+++ /dev/null
-===
-AAA
-===
-
-1. Project PTL: Ryan Goulding, ryandgoulding@gmail.com, rgoulding
-
- - Yes, I have reviewed the PTL Requirements [1]_
-
-2. Project Contact: Ryan Goulding, ryandgoulding@gmail.com, rgoulding
-
-3. Test Contact: Ryan Goulding, ryandgoulding@gmail.com, rgoulding
-
-4. Documentation Contact: Ryan Goulding, ryandgoulding@gmail.com, rgoulding
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? Yes
-
- - Committer lists were updated.
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-7. Does your project have any special needs in CI Infrastructure [2]_? No
-
-8. Is your project release plan finalized? Yes
-
- - `Release plan <https://wiki.opendaylight.org/view/AAA:Oxygen_Release_Plan>`_
-
-9. Do you have all APIs intended to be externally consumable listed?
-
- - Does each API have a useful short name? *Yes*
- - Are the Java interface and/or YANG files listed for each API? *Yes*
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? *Yes*
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? *Yes*
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Yes
-
- - controller, Implicit acknowledgement
- - mdsal, Implicit acknowledgement
- - odlparent, Implicit acknowledgement
- - yangtools, Implicit acknowledgement
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
-
-.. [1] Be sure to read the responsibilities of being a project lead under
- Leadership & Communication in the Requirements for Participation section
- of the release plan:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan#Requirements_for_Participation
-.. [2] Special needs include tools or configuration. Note that generally, the
- only available tools in CI are basic RHEL/CentOS linux images with Java.
- You should note and ask for anything beyond that here. Email
- helpdesk@opendaylight.org
+++ /dev/null
-====
-ALTO
-====
-
-1. Project PTL: Kai Gao, gaok12@mails.tsinghua.edu.cn, kaigao
-
-2. Project Contact: Jingxuan Zhang (Jensen), jingxuan.zhang@tongji.edu.cn, jensen_zhang
-
-3. Test Contact: Xiao Lin, xiao.lin@tongji.edu.cn, ShawnLin
-
-4. Documentation Contact: Kai Gao, gaok12@mails.tsinghua.edu.cn, kaigao
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-7. Does your project have any special needs in CI Infrastructure? No
-
-8. Is your project release plan finalized? No
-
- - ETA is by M2 status
-
-9. Do you have all APIs intended to be externally consumable listed? (Yes/No/Not Applicable)
-
- - Does each API have a useful short name? Yes
- - Are the Java interface and/or YANG files listed for each API? Yes
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? Yes
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? Yes
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Yes
-
- - Dependencies: l2switch, openflow-plugin
- - The dependent projects have been acknowledged in previous releases.
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
+++ /dev/null
-===========
-BGP PCEP LS
-===========
-
-1. Project PTL: Claudio David Gasparini, claudio.gasparini@pantheon.tech, cgasparini
-
- - Yes, I have reviewed the PTL Requirements
-
-2. Project Contact: Claudio David Gasparini, claudio.gasparini@pantheon.tech, cgasparini
-
-3. Test Contact: Vratko Polak, vrpolak@cisco.com, vrpolak
-
-4. Documentation Contact: Claudio David Gasparini, claudio.gasparini@pantheon.tech, cgasparini
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-7. Does your project have any special needs in CI Infrastructure? No
-
-8. Is your project release plan finalized? No
-
- - Eta is by m2 status
-
-9. Do you have all APIs intended to be externally consumable listed?
-
- - Does each API have a useful short name? Yes
- - Are the Java interface and/or YANG files listed for each API? Yes
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? Yes
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? Yes
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Yes
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
+++ /dev/null
-====
-BIER
-====
-
-1. Project PTL: Quan Xiong, xiong.quan@zte.com.cn, xiongquan
-
- - Yes, I have reviewed the PTL Requirements
-
-2. Project Contact: Quan Xiong, xiong.quan@zte.com.cn, xiongquan
-
-3. Test Contact: Quan Xiong, xiong.quan@zte.com.cn, xiongquan
-
-4. Documentation Contact: Quan Xiong, xiong.quan@zte.com.cn, xiongquan
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-7. Does your project have any special needs in CI Infrastructure? No
-
-8. Is your project release plan finalized? Yes
-
- - https://wiki.opendaylight.org/view/BIER:Oxygen:Release_Plan
-
-9. Do you have all APIs intended to be externally consumable listed?
-
- - Does each API have a useful short name? Yes
- - Are the Java interface and/or YANG files listed for each API? Yes
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? Yes
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? Yes
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Yes
-
- - controller,mdsal,NETCONF,YANGTOOL,dlux,odlparent,BGPCEP
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
+++ /dev/null
-===
-COE
-===
-
-1. Project PTL: Prem Sankar G, prem.sankar.g@ericsson.com, premsankar
-
- - Yes, I have reviewed the PTL Requirements.
-
-2. Project Contact: Prem Sankar G, prem.sankar.g@ericsson.com, premsankar
-
-3. Test Contact: Prem Sankar G, prem.sankar.g@ericsson.com, premsankar
-
-4. Documentation Contact: Faseela K, faseela.k@ericsson.com, faseelak
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-7. Does your project have any special needs in CI Infrastructure? No
-
-8. Is your project release plan finalized? Yes
-
- - https://wiki.opendaylight.org/view/Coe:Oxygen_Release_Plan
-
-9. Do you have all APIs intended to be externally consumable listed?
-
- - Does each API have a useful short name? Yes
- - Are the Java interface and/or YANG files listed for each API? Yes
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? Yes. They are all labelled as provisional.
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? Yes
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Yes
-
- - odlparent
- - YANG tools
- - mdsal
- - controller
-
-11. Will your project have top-level features not requiring system test? Yes
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? No
-
- - Coe only includes unit tests for top-level features.
- System tests require k8s and are needed by other ODL dependent project
- like netvirt. System test will be covered by ODL netvirt.
+++ /dev/null
-==========
-Controller
-==========
-
-1. Project PTL: Tom Pantelis, tompantelis@gmail.com
-
- - Yes, I have reviewed the PTL Requirements
-
-2. Project Contact: Tom Pantelis, tompantelis@gmail.com
-
-3. Test Contact: Vratko Polak, vrpolak@cisco.com, vrpolak
-
-4. Documentation Contact: Tom Pantelis, tompantelis@gmail.com
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-7. Does your project have any special needs in CI Infrastructure? No
-
-8. Is your project release plan finalized? Yes
-
- - https://wiki.opendaylight.org/view/OpenDaylight_Controller:Oxygen:Release_Plan
-
-9. Do you have all APIs intended to be externally consumable listed? Not Applicable
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Yes
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
+++ /dev/null
-======
-DAEXIM
-======
-
-1. Project PTL: Shaleen Saxena, shaleen.external@gmail.com, ssaxena
-
- - I have reviewed the PTL Requirements
-
-2. Project Contact: Shaleen Saxena, shaleen.external@gmail.com, ssaxena
-
-3. Test Contact: Sreekalyan Devaraj, kalyan.ds@gmail.com, sdevaraj
-
-4. Documentation Contact: Shaleen Saxena, shaleen.external@gmail.com, ssaxena
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-7. Does your project have any special needs in CI Infrastructure [2]_? No
-
-8. Is your project release plan finalized? Yes
-
- - https://wiki.opendaylight.org/view/Daexim:Oxygen:Release_Plan
-
-9. Do you have all APIs intended to be externally consumable listed? Not Applicable
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Yes
-
- - Dependencies are on standard Offset 0 Projects.
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
-
-**FOR NEW PROJECTS ONLY**
-
-Not applicable
-
-
-.. [1] Be sure to read the responsibilities of being a project lead under
- Leadership & Communication in the Requirements for Participation section
- of the release plan:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan#Requirements_for_Participation
-.. [2] Special needs include tools or configuration. Note that generally, the
- only available tools in CI are basic RHEL/CentOS linux images with Java.
- You should note and ask for anything beyond that here. Email
- helpdesk@opendaylight.org
-.. [3] It is recommended to use the OpenDaylight CI infrastructure unless there
- is some HW or SW resource that cannot be installed there. Update the
- test plan with explanation on why your top-level features will not be
- using the OpenDaylight CI Infrastructure:
- https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template#Test_Infrastructure
-.. [4] Projects running system test in external Labs are required to report
- system test results in a timely fashion after release creations, e.g.,
- weekly, RC, and formal releases. Update the test plan with plans on
- testing in external lab:
- https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template#Test_Infrastructure
-.. [5] https://wiki.opendaylight.org/view/Template:Project_Facts
-.. [6] https://wiki.opendaylight.org/view/GettingStarted:Project_Main#New_Project_Checklist
+++ /dev/null
-========================
-Integration/Distribution
-========================
-
-1. Project PTL: Vratko Polak, vrpolak@cisco.com, vrpolak
-
- - I have reviewed the PTL Requirements [1]_: True.
-
-2. Project Contact: Luis Gomez, ecelgp@gmail.com, LuisGomez
-
-3. Test Contact: Vratko Polak, vrpolak@cisco.com, vrpolak
-
-4. Documentation Contact: Luis Gomez, ecelgp@gmail.com, LuisGomez
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? Yes
-
-7. Does your project have any special needs in CI Infrastructure [2]_? No
-
-8. Is your project release plan finalized? Yes
-
- - [7]_.
-
-9. Do you have all APIs intended to be externally consumable listed? Yes
-
- - Does each API have a useful short name? Yes
- - Are the Java interface and/or YANG files listed for each API? Yes
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? Yes
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? Yes
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Yes
-
- - Zero requests
-
-11. Will your project have top-level features not requiring system test? Yes
-
- - legacy experimental scripts
- - no waiver requested
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
-
-.. [1] Be sure to read the responsibilities of being a project lead under
- Leadership & Communication in the Requirements for Participation section
- of the release plan:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan#Requirements_for_Participation
-.. [2] Special needs include tools or configuration. Note that generally, the
- only available tools in CI are basic RHEL/CentOS linux images with Java.
- You should note and ask for anything beyond that here. Email
- helpdesk@opendaylight.org
-.. [3] It is recommended to use the OpenDaylight CI infrastructure unless there
- is some HW or SW resource that cannot be installed there. Update the
- test plan with explanation on why your top-level features will not be
- using the OpenDaylight CI Infrastructure:
- https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template#Test_Infrastructure
-.. [4] Projects running system test in external Labs are required to report
- system test results in a timely fashion after release creations, e.g.,
- weekly, RC, and formal releases. Update the test plan with plans on
- testing in external lab:
- https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template#Test_Infrastructure
-.. [5] https://wiki.opendaylight.org/view/Template:Project_Facts
-.. [6] https://wiki.opendaylight.org/view/GettingStarted:Project_Main#New_Project_Checklist
-.. [7] https://wiki.opendaylight.org/view/Integration/Distribution/Oxygen_Release_Plan
+++ /dev/null
-====
-Dlux
-====
-
-1. Project PTL: Maxime Millette Coulombe, mmcoulombe@inocybe.com, mmcoulombe
-
- - I have reviewed the PTL Requirements
-
-2. Project Contact: Daniel Malachovsky, dmalacho@cisco.com, malachovsky
-
-3. Test Contact: Daniel Malachovsky, dmalacho@cisco.com, malachovsky
-
-4. Documentation Contact: Daniel Malachovsky, dmalacho@cisco.com, malachovsky
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-7. Does your project have any special needs in CI Infrastructure? No
-
-8. Is your project release plan finalized? Yes
-
- - https://wiki.opendaylight.org/view/OpenDaylight_dlux:Oxygen_Release_Plan
-
-9. Do you have all APIs intended to be externally consumable listed? Not Applicable
-
- - Does each API have a useful short name? NA
- - Are the Java interface and/or YANG files listed for each API? NA
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? NA
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? NA
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? No
-
- - No requests on upstream projects
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
+++ /dev/null
-========
-DLuxApps
-========
-
-1. Project PTL: Daniel Malachovsky, dmalacho@cisco.com, malachovsky
-
- - I have reviewed the PTL Requirements
-
-2. Project Contact: Daniel Malachovsky, dmalacho@cisco.com, malachovsky
-
-3. Test Contact: Lubomir Balogh, lubalogh@cisco.com, lubalogh
-
-4. Documentation Contact: Daniel Malachovsky, dmalacho@cisco.com, malachovsky
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-7. Does your project have any special needs in CI Infrastructure? No
-
-8. Is your project release plan finalized? Yes
-
- - https://wiki.opendaylight.org/view/DluxApps:Oxygen_Release_Plan
-
-9. Do you have all APIs intended to be externally consumable listed? Not Applicable
-
- - Does each API have a useful short name? NA
- - Are the Java interface and/or YANG files listed for each API? NA
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? NA
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? NA
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? No
-
- - No requests on upstream projects
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
+++ /dev/null
-====
-Eman
-====
-
-1. Project PTL: Frank Sandoval, francisrsandoval@gmail.com, francisrsandoval
-
- - I have reviewed the PTL Requirements Yes
-
-2. Project Contact: Frank Sandoval, francisrsandoval@gmail.com, francisrsandoval
-
-3. Test Contact: Frank Sandoval, francisrsandoval@gmail.com, francisrsandoval
-
-4. Documentation Contact: Frank Sandoval, francisrsandoval@gmail.com, francisrsandoval
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-7. Does your project have any special needs in CI Infrastructure? No
-
-8. Is your project release plan finalized? No
-
- - 11/3/2017
-
-9. Do you have all APIs intended to be externally consumable listed? Yes
-
- - Does each API have a useful short name? Yes
- - Are the Java interface and/or YANG files listed for each API? Yes
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? Yes
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? Yes
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Yes
-
- -There are no dependencies
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
+++ /dev/null
-====
-FaaS
-====
-
-1. Project PTL: Xingjun Chu, xingjun.chu@huawei.com, xingjun
-
- - I have reviewed the PTL Requirements
-
-2. Project Contact: Xingjun Chu, xingjun.chu@huawei.com, xingjun
-
-3. Test Contact: Xingjun Chu, xingjun.chu@huawei.com, xingjun
-
-4. Documentation Contact: Xingjun Chu, xingjun.chu@huawei.com, xingjun
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No
-
-7. Does your project have any special needs in CI Infrastructure? No
-
-8. Is your project release plan finalized? Yes
-
- - https://wiki.opendaylight.org/view/FaaS:Oxygen_Release_Plan
-
-9. Do you have all APIs intended to be externally consumable listed? Yes
-
- - Does each API have a useful short name? Yes
- - Are the Java interface and/or YANG files listed for each API? Yes
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? Yes
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? Yes
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Yes
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
+++ /dev/null
-======
-Genius
-======
-
-1. Project PTL: Vivek Srivastava, vivek.v.srivastava@ericsson.com, viveks
-
- - Yes, I have reviewed the PTL Requirements [1]_
-
-2. Project Contact: Faseela K., faseela.k@ericsson.com, faseela
-
-3. Test Contact: Vidya Sathyanarayanachar, vidya.s@altencalsoftlabs.com
-
-4. Documentation Contact: Vishal Thapar, vishal.thapar@ericsson.com, vthapar
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-7. Does your project have any special needs in CI Infrastructure [2]_? No
-
-8. Is your project release plan finalized? Yes
-
- - `Release plan <https://wiki.opendaylight.org/view/Genius:Oxygen_Release_Plan>`_
-
-9. Do you have all APIs intended to be externally consumable listed? Yes
-
- - Does each API have a useful short name? Yes
- - Are the Java interface and/or YANG files listed for each API? Yes
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? No
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? Yes
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Yes
-
- - Dependencies: YANG Tools, MDSAL, OVSDB, OpenflowPlugin, Odlparent, Controller, Infrautils
- - Dependent projects have been acknowledged in previous releases.
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
-
-.. [1] Be sure to read the responsibilities of being a project lead under
- Leadership & Communication in the Requirements for Participation section
- of the release plan:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan#Requirements_for_Participation
-.. [2] Special needs include tools or configuration. Note that generally, the
- only available tools in CI are basic RHEL/CentOS linux images with Java.
- You should note and ask for anything beyond that here. Email
- helpdesk@opendaylight.org
-.. [3] It is recommended to use the OpenDaylight CI infrastructure unless there
- is some HW or SW resource that cannot be installed there. Update the
- test plan with explanation on why your top-level features will not be
- using the OpenDaylight CI Infrastructure:
- https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template#Test_Infrastructure
-.. [4] Projects running system test in external Labs are required to report
- system test results in a timely fashion after release creations, e.g.,
- weekly, RC, and formal releases. Update the test plan with plans on
- testing in external lab:
- https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template#Test_Infrastructure
-.. [5] https://wiki.opendaylight.org/view/Template:Project_Facts
-.. [6] https://wiki.opendaylight.org/view/GettingStarted:Project_Main#New_Project_Checklist
+++ /dev/null
-==================
-Group Based Policy
-==================
-
-1. Project PTL: Michal Cmarada, mcmarada@cisco.com, michal-cmarada
-
-2. Project Contact: Michal Cmarada, mcmarada@cisco.com, michal-cmarada
-
-3. Test Contact: Tomas Cechvala, tcechval@cisco.com, tomas_c
-
-4. Documentation Contact: Michal Cmarada, mcmarada@cisco.com, michal-cmarada
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-7. Does your project have any special needs in CI Infrastructure? Yes
-
- - We need NSH (Network Service Header) support in OVS (OpenVSwitch) for some test cases. see `Bug-8488 <https://bugs.opendaylight.org/show_bug.cgi?id=8488>`_
-
-8. Is your project release plan finalized? Yes
-
- - Available here: `Release plan <https://wiki.opendaylight.org/view/Group_Based_Policy_(GBP)/Releases/Oxygen/Release_plan>`_
-
-9. Do you have all APIs intended to be externally consumable listed? Yes
-
- - Does each API have a useful short name? Yes
- - Are the Java interface and/or YANG files listed for each API? Yes
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? Yes
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? Yes
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Yes
-
- - Dependencies: aaa,controller,dlux,faas,honeycomb/vbd,lispflowmapping,mdsal,netconf,neutron,odlparent,openflowplugin,ovsdb,sfc,sxp
- - Yes. The dependent projects have been acknowledged in previous releases.
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
-
- - There are tests for top level features that are provided via
- `OPNFV (Open Platform for Network Functions Virtualization) pipeline. <http://testresults.opnfv.org/>`_
- Documentation for testing via OPNFV is available here: `FDS (FastDataStacks) Testing Euphrates <https://wiki.opnfv.org/display/fds/FDS+Testing+Euphrates>`_
+++ /dev/null
-=============
-Honeycomb/VBD
-=============
-
-1. Project PTL: Michal Cmarada, mcmarada@cisco.com, michal-cmarada
-
-2. Project Contact: Michal Cmarada, mcmarada@cisco.com, michal-cmarada
-
-3. Test Contact: Michal Cmarada, mcmarada@cisco.com, michal-cmarada
-
-4. Documentation Contact: Michal Cmarada, mcmarada@cisco.com, michal-cmarada
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-7. Does your project have any special needs in CI Infrastructure? No
-
-8. Is your project release plan finalized? Yes
-
- - Available here: `Release plan <https://wiki.opendaylight.org/view/Honeycomb/VBD/Oxygen/Release_Plan>`_
-
-9. Do you have all APIs intended to be externally consumable listed? Yes
-
- - Does each API have a useful short name? Yes
- - Are the Java interface and/or YANG files listed for each API? Yes
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? Yes
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? Yes
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Yes
-
- - Dependencies: dlux,dluxapps,mdsal,netconf,odlparent
- - Yes. The dependent projects have been acknowledged in previous releases.
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? No
-
- - There are tests for top level features that are provided via
- `OPNFV (Open Platform for Network Functions Virtualization) pipeline. <http://testresults.opnfv.org/>`_
- Documentation for testing via OPNFV is available here: `FDS (FastDataStacks) Testing Euphrates <https://wiki.opnfv.org/display/fds/FDS+Testing+Euphrates>`_
+++ /dev/null
-==========
-InfraUtils
-==========
-
-1. Project PTL: Michael Vorburger, vorburger@redhat.com, vorburger
-
- - I have reviewed the PTL Requirements [1]_
-
-2. Project Contact: Michael Vorburger, vorburger@redhat.com, vorburger
-
-3. Test Contact: N/A
-
- - InfraUtils get tested by users of the utilities
-
-4. Documentation Contact: Faseela K, faseela.k@ericsson.com, faseelak
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-7. Does your project have any special needs in CI Infrastructure [2]_? No
-
-8. Is your project release plan finalized? Yes
-
- - `Release plan <https://wiki.opendaylight.org/view/InfraUtils:Oxygen:Release_Plan>`_
-
-9. Do you have all APIs intended to be externally consumable listed? Yes
-
- - Does each API have a useful short name? Yes
- - Are the Java interface and/or YANG files listed for each API? Yes
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? Yes
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? Yes
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Yes
-
- - odlparent, Implicit acknowledgement
-
-11. Will your project have top-level features not requiring system test? Yes
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? No
-
-.. [1] Be sure to read the responsibilities of being a project lead under
- Leadership & Communication in the Requirements for Participation section
- of the release plan:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan#Requirements_for_Participation
-.. [2] Special needs include tools or configuration. Note that generally, the
- only available tools in CI are basic RHEL/CentOS linux images with Java.
- You should note and ask for anything beyond that here. Email
- helpdesk@opendaylight.org
+++ /dev/null
-========
-JSON-RPC
-========
-
-1. Project PTL: Anton Ivanov, anton.ivanov@cambridgegreys.com, kot-begemot
-
- - I have reviewed the PTL Requirements
-
-2. Project Contact: Anton Ivanov, anton.ivanov@cambridgegreys.com, kot-begemot
-
-3. Test Contact: Anton Ivanov, anton.ivanov@cambridgegreys.com, kot-begemot
-
-4. Documentation Contact: Anton Ivanov, anton.ivanov@cambridgegreys.com, kot-begemot
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? Yes
-
-7. Does your project have any special needs in CI Infrastructure [2]_? No
-
-8. Is your project release plan finalized? Yes
-
- - https://wiki.opendaylight.org/view/JsonRPC2.0:Oxygen:Release_Plan
-
-9. Do you have all APIs intended to be externally consumable listed? Not Applicable
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Yes
-
- - Offset 0 projects: MDSAL, yangtools, controller
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
-
-**FOR NEW PROJECTS ONLY**
-
-Not Applicable - while this is first release, project has been part of ODL
-since Boron.
-
-.. [1] Be sure to read the responsibilities of being a project lead under
- Leadership & Communication in the Requirements for Participation section
- of the release plan:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan#Requirements_for_Participation
-.. [2] Special needs include tools or configuration. Note that generally, the
- only available tools in CI are basic RHEL/CentOS linux images with Java.
- You should note and ask for anything beyond that here. Email
- helpdesk@opendaylight.org
-.. [3] It is recommended to use the OpenDaylight CI infrastructure unless there
- is some HW or SW resource that cannot be installed there. Update the
- test plan with explanation on why your top-level features will not be
- using the OpenDaylight CI Infrastructure:
- https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template#Test_Infrastructure
-.. [4] Projects running system test in external Labs are required to report
- system test results in a timely fashion after release creations, e.g.,
- weekly, RC, and formal releases. Update the test plan with plans on
- testing in external lab:
- https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template#Test_Infrastructure
-.. [5] https://wiki.opendaylight.org/view/Template:Project_Facts
-.. [6] https://wiki.opendaylight.org/view/GettingStarted:Project_Main#New_Project_Checklist
+++ /dev/null
-=========
-L2 Switch
-=========
-
-1. Project PTL: Sai MarapaReddy, sai.marapareddy@gmail.com, sai_marapareddy
-
- - I have reviewed the PTL Requirements [1]_ Yes
-
-2. Project Contact: Evan Zeller, evanrzeller@gmail.com, evanz
-
-3. Test Contact: Evan Zeller, evanrzeller@gmail.com, evanz
-
-4. Documentation Contact: Evan Zeller, evanrzeller@gmail.com, evanz
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? Yes
-
-7. Does your project have any special needs in CI Infrastructure [2]_? No
-
-8. Is your project release plan finalized? Yes
-
- - release_plan_
-
-9. Do you have all APIs intended to be externally consumable listed? Yes
-
- - Does each API have a useful short name? (Yes/No) *Yes*
- - Are the Java interface and/or YANG files listed for each API? (Yes/No) *Yes*
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? *No*
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? (Yes/No) *No*
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Yes
-
- - openflowplugin, acknowledged
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
-
-.. [1] Be sure to read the responsibilities of being a project lead under
- Leadership & Communication in the Requirements for Participation section
- of the release plan:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan#Requirements_for_Participation
-.. [2] Special needs include tools or configuration. Note that generally, the
- only available tools in CI are basic RHEL/CentOS linux images with Java.
- You should note and ask for anything beyond that here. Email
- helpdesk@opendaylight.org
-
-.. _release_plan: https://wiki.opendaylight.org/view/L2_Switch:Oxygen_Release_Plan
+++ /dev/null
-=================
-LISP Flow Mapping
-=================
-
-1. Project PTL: Vina Ermagan, vermagan@cisco.com, vina_ermagan
-
- - Yes. I have reviewed the PTL Requirements.
-
-2. Project Contact: Vina Ermagan, vermagan@cisco.com, vina_ermagan
-
- - and Lori Jakab, lojakab@cisco.com, lori
-
-3. Test Contact: Lori Jakab, lojakab@cisco.com, lori
-
-4. Documentation Contact: Vina Ermagan, vermagan@cisco.com, vina_ermagan
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-7. Does your project have any special needs in CI Infrastructure? No
-
-8. Is your project release plan finalized? Yes
-
- - https://wiki.opendaylight.org/view/OpenDaylight_Lisp_Flow_Mapping:Oxygen_Release_Plan
-
-9. Do you have all APIs intended to be externally consumable listed? Yes
-
- - Does each API have a useful short name? Yes
- - Are the Java interface and/or YANG files listed for each API? Yes
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? Yes
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? Yes
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Yes. No Changes since last release.
-
- - General dependencies:
-
- 1. odlparent
- 2. yangtools
- 3. controller
- 4. netconf
- 5. mdsal
- 6. honeycomb/vbd
- 7. neutron
- 8. dlux / dluxApps
-
-11. Will your project have top-level features not requiring system test?
- No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
+++ /dev/null
-======
-MD-SAL
-======
-
-1. Project PTL: Robert Varga, robert.varga@pantheon.tech, rovarga
-
- - Yes, I have reviewed the PTL Requirements
-
-2. Project Contact: Robert Varga, robert.varga@pantheon.tech, rovarga
-
-3. Test Contact: Vratko Polak, vrpolak@cisco.com, vrpolak
-
-4. Documentation Contact: Robert Varga, robert.varga@pantheon.tech, rovarga
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-7. Does your project have any special needs in CI Infrastructure? No
-
-8. Is your project release plan finalized? No
-
- - ETA is 11/25. We know there will be no major new features.
-
-9. Do you have all APIs intended to be externally consumable listed? Yes
-
- - Does each API have a useful short name? Yes
- - Are the Java interface and/or YANG files listed for each API? Yes
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? Yes
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? Yes
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Yes
-
-11. Will your project have top-level features not requiring system test? Yes
-
- - Experimental features, waiver TBD
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
+++ /dev/null
-====
-NEMO
-====
-
-1. Project PTL: A H, an.ho@huawei.com, anipbu
-
- - Yes, I have reviewed the PTL Requirements.
-
-2. Project Contact: A H, an.ho@huawei.com, anipbu
-
-3. Test Contact: A H, an.ho@huawei.com, anipbu
-
-4. Documentation Contact: A H, an.ho@huawei.com, anipbu
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No
-
-7. Does your project have any special needs in CI Infrastructure? No
-
-8. Is your project release plan finalized? Yes
-
- - `Release plan <https://wiki.opendaylight.org/view/NEMO:Oxygen:Release_Plan>`_
-
-9. Do you have all APIs intended to be externally consumable listed?
-
- - Does each API have a useful short name? *Yes*
- - Are the Java interface and/or YANG files listed for each API? *Yes*
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? *Yes*
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? *Yes*
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Yes
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
+++ /dev/null
-=======
-NETCONF
-=======
-
-1. Project PTL: Tomas Cere, tcere@cisco.com, tcere
-
- - Yes, I have reviewed the PTL Requirements.
-
-2. Project Contact: Tomas Cere, tcere@cisco.com, tcere
-
-3. Test Contact: Vratko Polak, vrpolak@cisco.com, vrpolak
-
-4. Documentation Contact: Tomas Cere, tcere@cisco.com, tcere
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-7. Does your project have any special needs in CI Infrastructure? No
-
-8. Is your project release plan finalized? No
-
-9. Do you have all APIs intended to be externally consumable listed?
-
- - Does each API have a useful short name? *Yes*
- - Are the Java interface and/or YANG files listed for each API? *Yes*
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? *Yes*
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? *Yes*
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Yes
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
+++ /dev/null
-=======
-NetVirt
-=======
-
-1. Project PTL: Sam Hague, shague@gmail.com, shague
-
- - Yes, I have reviewed the PTL Requirements [1]_.
-
-2. Project Contact: Sam Hague, shague@gmail.com, shague
-
-3. Test Contact: Jamo Luhrsen, jluhrsen@redhat.com, jamoluhrsen
-
-4. Documentation Contact: Vishal Thapar, vthapar@ericsson.com, vthapar
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-7. Does your project have any special needs in CI Infrastructure [2]_? No
-
-8. Is your project release plan finalized? Yes
-
- - `Release plan <https://wiki.opendaylight.org/view/NetVirt:Oxygen:Release_Plan>`_
-
-9. Do you have all APIs intended to be externally consumable listed?
-
- - Does each API have a useful short name? *Yes*
- - Are the Java interface and/or YANG files listed for each API? *Yes*
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? *Yes*
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? *Yes*
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? No
-
- - controller, Implicit acknowledgement
- - mdsal, Implicit acknowledgement
- - odlparent, Implicit acknowledgement
- - yangtools, Implicit acknowledgement
- - genius
- - sfc
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? No
-
-.. [1] Be sure to read the responsibilities of being a project lead under
- Leadership & Communication in the Requirements for Participation section
- of the release plan:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan#Requirements_for_Participation
-.. [2] Special needs include tools or configuration. Note that generally, the
- only available tools in CI are basic RHEL/CentOS linux images with Java.
- You should note and ask for anything beyond that here. Email
- helpdesk@opendaylight.org
+++ /dev/null
-==================
-Neutron Northbound
-==================
-
-1. Project PTL: Isaku Yamahata, isaku.yamahata@gmail.com, yamahata
-
- - Yes, I have reviewed the PTL Requirements.
-
-2. Project Contact: Isaku Yamahata, isaku.yamahata@gmail.com, yamahata
-
-3. Test Contact: Pramod Raghavendra Jayathirth, pramod.raghavendra.jayathirth@intel.com, pramodrj07
-
-4. Documentation Contact: Pramod Raghavendra Jayathirth, pramod.raghavendra.jayathirth@intel.com, pramodrj07
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-7. Does your project have any special needs in CI Infrastructure? No
-
-8. Is your project release plan finalized? Yes
-
- - `Release plan <https://wiki.opendaylight.org/view/NeutronNorthbound:Oxygen_Release_Plan>`_
-
-9. Do you have all APIs intended to be externally consumable listed?
-
- - Does each API have a useful short name? *Yes*
- - Are the Java interface and/or YANG files listed for each API? *Yes*
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? *Yes*
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? *Yes*
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? No
-
- - odlparent
- - YANG tools
- - mdsal
- - controller
- - netconf
- - ovsdb
-
-
-11. Will your project have top-level features not requiring system test? Yes
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? No
+++ /dev/null
-===
-NIC
-===
-
-1. Project PTL: Yrineu Rodrigues, yrineu.rodrigues@serro.com, yrineu_rodrigues
-
- - Yes, I have reviewed the PTL Requirements [1]_.
-
-2. Project Contact: Yrineu Rodrigues, yrineu.rodrigues@serro.com, yrineu_rodrigues
-
-3. Test Contact: Carmen Kelling, carmen.kelling@gmail.com, carmen_kelling
-
-4. Documentation Contact: Yrineu Rodrigues, yrineu.rodrigues@serro.com, yrineu_rodrigues
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No deliverables
-
-7. Does your project have any special needs in CI Infrastructure? No
-
-8. Is your project release plan finalized? Yes
-
- - `Release plan <https://wiki.opendaylight.org/view/NIC:Oxygen:Release_Plan>`_
-
-9. Do you have all APIs intended to be externally consumable listed?
-
- - Does each API have a useful short name? *Yes*
- - Are the Java interface and/or YANG files listed for each API? *Yes*
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? *Yes*
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? *Yes*
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects?
-
- - controller, Implicit acknowledgement
- - mdsal, Implicit acknowledgement
- - odlparent, Implicit acknowledgement
- - yangtools, Implicit acknowledgement
- - genius
- - openflow-plugin
- - bgpcep
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? No
-
-.. [1] Be sure to read the responsibilities of being a project lead under
- Leadership & Communication in the Requirements for Participation section
- of the release plan:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan#Requirements_for_Participation
-.. [2] NIC main page: https://wiki.opendaylight.org/view/Network_Intent_Composition:Main
+++ /dev/null
-==========
-ODL Parent
-==========
-
-1. Project PTL: Stephen Kitt, skitt@redhat.com, skitt
-
- - Yes, I have reviewed the PTL Requirements.
-
-2. Project Contact: Stephen Kitt, skitt@redhat.com, skitt
-
-3. Test Contact: Stephen Kitt, skitt@redhat.com, skitt
-
-4. Documentation Contact: Stephen Kitt, skitt@redhat.com, skitt
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No deliverables
-
-7. Does your project have any special needs in CI Infrastructure? No
-
-8. Is your project release plan finalized? Yes
-
- - `Release plan <https://wiki.opendaylight.org/view/ODL_Parent:Oxygen_Release_Plan>`_
-
-9. Do you have all APIs intended to be externally consumable listed? Yes
-
- - Does each API have a useful short name? *Yes*
- - Are the Java interface and/or YANG files listed for each API? *Not applicable*
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? *Yes*
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? *Yes*
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Not Applicable
-
-11. Will your project have top-level features not requiring system test? Yes
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? No
+++ /dev/null
-=========
-OF-CONFIG
-=========
-
-1. Project PTL: Wei Meng, meng.wei2@zte.com.cn, valley
-
- - Yes, I have reviewed the PTL Requirements
-
-2. Project Contact: Wei Meng, meng.wei2@zte.com.cn, valley
-
-3. Test Contact: Wei Meng, meng.wei2@zte.com.cn, valley
-
-4. Documentation Contact: Wei Meng, meng.wei2@zte.com.cn, valley
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-7. Does your project have any special needs in CI Infrastructure? No
-
-8. Is your project release plan finalized? Yes
-
- - `Release plan <https://wiki.opendaylight.org/view/OF-CONFIG:Oxygen:Release_Plan>`_
-
-9. Do you have all APIs intended to be externally consumable listed?
-
- - Does each API have a useful short name? *Yes*
- - Are the Java interface and/or YANG files listed for each API? *Yes*
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? *Yes*
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? *Yes*
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Yes
-
- - controller
- - mdsal
- - NETCONF
- - YANGTOOL
- - dlux
- - odlparent
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
+++ /dev/null
-===============
-OpenFlow Plugin
-===============
-
-1. Project PTL: Abhijit Kumbhare, abhijitkoss@gmail.com, abhijitkumbhare
-
- - Yes, I have reviewed the PTL Requirements [1]_.
-
-2. Project Contact: Abhijit Kumbhare, abhijitkoss@gmail.com, abhijitkumbhare
-
-3. Test Contact: Luis Gomez, ecelgp@gmail.com, LuisGomez
-
-4. Documentation Contact: Shuva Jyoti Kar, shuva.jyoti.kar.87@gmail.com, shuva
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? Yes
-
-7. Does your project have any special needs in CI Infrastructure [2]_? No
-
-8. Is your project release plan finalized? Yes
-
- - `Release plan <https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:Oxygen_Release_Plan>`_
-
-9. Do you have all APIs intended to be externally consumable listed? Yes
-
- - Does each API have a useful short name? Yes
- - Are the Java interface and/or YANG files listed for each API? Yes
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? Yes
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? Yes
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Yes
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
-
-**FOR NEW PROJECTS ONLY**
-
-A. Project Main Page: (wiki link)
-
- - Use Project Facts Template [5]_
-
-B. Have you completed the project checklist [6]_? (Yes/No)
-
- - (link to a merged patch in gerrit)
- - (link to a mail from your mailing list)
- - (link to a bug for your project; you can create a dummy one and close it if need be)
- - (link to an artifact published from your project in nexus)
- - (link to a sonar report)
- - (link to your root pom file)
-
-.. [1] Be sure to read the responsibilities of being a project lead under
- Leadership & Communication in the Requirements for Participation section
- of the release plan:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan#Requirements_for_Participation
-.. [2] Special needs include tools or configuration. Note that generally, the
- only available tools in CI are basic RHEL/CentOS linux images with Java.
- You should note and ask for anything beyond that here. Email
- helpdesk@opendaylight.org
-.. [3] It is recommended to use the OpenDaylight CI infrastructure unless there
- is some HW or SW resource that cannot be installed there. Update the
- test plan with explanation on why your top-level features will not be
- using the OpenDaylight CI Infrastructure:
- https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template#Test_Infrastructure
-.. [4] Projects running system test in external Labs are required to report
- system test results in a timely fashion after release creations, e.g.,
- weekly, RC, and formal releases. Update the test plan with plans on
- testing in external lab:
- https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template#Test_Infrastructure
-.. [5] https://wiki.opendaylight.org/view/Template:Project_Facts
-.. [6] https://wiki.opendaylight.org/view/GettingStarted:Project_Main#New_Project_Checklist
+++ /dev/null
-======
-OpFlex
-======
-
-1. Project PTL: Rob Adams, readams@readams.net, readams
-
- - Yes, I have reviewed the PTL Requirements.
-
-2. Project Contact: Rob Adams, readams@readams.net, readams
-
-3. Test Contact: Rob Adams, readams@readams.net, readams
-
-4. Documentation Contact: Rob Adams, readams@readams.net, readams
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No deliverables
-
-7. Does your project have any special needs in CI Infrastructure ? No
-
-8. Is your project release plan finalized? No
-
-9. Do you have all APIs intended to be externally consumable listed?
-
- - Does each API have a useful short name? *Not Applicable*
- - Are the Java interface and/or YANG files listed for each API? *Not Applicable*
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? *Not Applicable*
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? *Not Applicable*
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Yes
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
+++ /dev/null
-=====
-OVSDB
-=====
-
-1. Project PTL: Anil Kumar Vishnoi, vishnoianil@gmail.com, vishnoianil
-
- - Yes, I have reviewed the PTL Requirements [1]_.
-
-2. Project Contact: Anil Kumar Vishnoi, vishnoianil@gmail.com, vishnoianil
-
-3. Test Contact: Jamo Luhrsen, jluhrsen@redhat.com, jamoluhrsen
-
-4. Documentation Contact: Anil Kumar Vishnoi, vishnoianil@gmail.com, vishnoianil
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-7. Does your project have any special needs in CI Infrastructure [2]_? No
-
-8. Is your project release plan finalized? Yes
-
- - `Release plan <https://wiki.opendaylight.org/view/OpenDaylight_OVSDB:Oxygen_Release_Plan>`_
-
-9. Do you have all APIs intended to be externally consumable listed?
-
- - Does each API have a useful short name? *Yes*
- - Are the Java interface and/or YANG files listed for each API? *Yes*
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? *Yes*
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? *Yes*
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects?
-
- - controller, Implicit acknowledgement
- - mdsal, Implicit acknowledgement
- - odlparent, Implicit acknowledgement
- - yangtools, Implicit acknowledgement
-
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
-
-.. [1] Be sure to read the responsibilities of being a project lead under
- Leadership & Communication in the Requirements for Participation section
- of the release plan:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan#Requirements_for_Participation
-.. [2] Special needs include tools or configuration. Note that generally, the
- only available tools in CI are basic RHEL/CentOS linux images with Java.
- You should note and ask for anything beyond that here. Email
- helpdesk@opendaylight.org
+++ /dev/null
-=========
-P4 Plugin
-=========
-
-1. Project PTL: Ding Rui, ding.rui@zte.com.cn, dingrui
-
- - Yes, I have reviewed the PTL Requirements.
-
-2. Project Contact: Ding Rui, ding.rui@zte.com.cn, dingrui
-
-3. Test Contact: Ding Rui, ding.rui@zte.com.cn, dingrui
-
-4. Documentation Contact: Ding Rui, ding.rui@zte.com.cn, dingrui
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-7. Does your project have any special needs in CI Infrastructure? Yes
-
-8. Is your project release plan finalized? Yes
-
- - `Release Plan <https://wiki.opendaylight.org/view/P4_Plugin:Oxygen:Release_Plan>`_
-
-9. Do you have all APIs intended to be externally consumable listed?
-
- - Does each API have a useful short name? *Yes*
- - Are the Java interface and/or YANG files listed for each API? *Yes*
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? *Yes*
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? *Yes*
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Yes
-
- - controller
- - mdsal
- - NETCONF
- - YANGTOOL
- - dlux
- - odlparent
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
+++ /dev/null
-===========
-PacketCable
-===========
-
-1. Project PTL: Steve Pisarski, s.pisarski@cablelabs.com, N/A
-
- - Yes, I have reviewed the PTL Requirements.
-
-2. Project Contact: Kevin Kershaw, k.kershaw@cablelabs.com, N/A
-
-3. Test Contact: Kevin Kershaw, k.kershaw@cablelabs.com, N/A
-
-4. Documentation Contact: Kevin Kershaw, k.kershaw@cablelabs.com, N/A
-
-5. Does your project have any updates on any previously-incomplete
- items from prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No planned deliverables
-
-7. Does your project have any special needs in CI Infrastructure? No
-
-8. Is your project release plan finalized? Yes
-
- - `Release plan <https://wiki.opendaylight.org/view/PacketCablePCMM:Release_Plan_Oxygen>`_
-
-9. Do you have all APIs intended to be externally consumable listed?
-
- - Does each API have a useful short name? *Yes*
- - Are the Java interface and/or YANG files listed for each API? *Yes*
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? *Yes*
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? *Yes*
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Not Applicable
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
+++ /dev/null
-=========================
-Service Function Chaining
-=========================
-
-1. Project PTL: Brady Johnson, bjohnson@inocybe.com, ebrjohn
- - Yes, I have reviewed the PTL Requirements [1]_.
-
-2. Project Contact: Brady Johnson, bjohnson@inocybe.com, ebrjohn
-
-3. Test Contact: Jaime Caamaño, jcaamano@suse.com, jaicaa
-
-4. Documentation Contact: David Suárez Fuentes, david.suarez.fuentes@gmail.com, edavsua
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-7. Does your project have any special needs in CI Infrastructure [2]_? No
-
-8. Is your project release plan finalized? Yes
-
- - `Release plan <https://wiki.opendaylight.org/view/Service_Function_Chaining:Oxygen_Release_Plan>`_
-
-9. Do you have all APIs intended to be externally consumable listed?
-
- - Does each API have a useful short name? *Yes*
- - Are the Java interface and/or YANG files listed for each API? *Yes*
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? *Yes*
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? *Yes*
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects?
-
- - controller, Implicit acknowledgement
- - mdsal, Implicit acknowledgement
- - odlparent, Implicit acknowledgement
- - yangtools, Implicit acknowledgement
- - openflowplugin, Not acknowledged in Oxygen yet
- - ovsdb, Not acknowledged in Oxygen yet
- - genius, Not acknowledged in Oxygen yet
- - LISP, Not acknowledged in Oxygen yet
-
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
-
-.. [1] Be sure to read the responsibilities of being a project lead under
- Leadership & Communication in the Requirements for Participation section
- of the release plan:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan#Requirements_for_Participation
-.. [2] Special needs include tools or configuration. Note that generally, the
- only available tools in CI are basic RHEL/CentOS linux images with Java.
- You should note and ask for anything beyond that here. Email
- helpdesk@opendaylight.org
+++ /dev/null
-====
-SNMP
-====
-
-1. Project PTL: Ryan Goulding, ryandgoulding@gmail.com, rgoulding
-
- - Yes, I have reviewed the PTL Requirements [1]_.
-
-2. Project Contact: Ryan Goulding, ryandgoulding@gmail.com, rgoulding
-
-3. Test Contact: Ryan Goulding, ryandgoulding@gmail.com, rgoulding
-
-4. Documentation Contact: Ryan Goulding, ryandgoulding@gmail.com, rgoulding
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? Yes.
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-7. Does your project have any special needs in CI Infrastructure [2]_? No
-
-8. Is your project release plan finalized? Yes
-
- - `Release plan <https://wiki.opendaylight.org/view/SNMP_Plugin:Oxygen_Release_Plan>`_
-
-9. Do you have all APIs intended to be externally consumable listed?
-
- - Does each API have a useful short name? *Yes*
- - Are the Java interface and/or YANG files listed for each API? *Yes*
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? *Yes*
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? *Yes*
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects?
-
- - controller, Implicit acknowledgement
- - mdsal, Implicit acknowledgement
- - odlparent, Implicit acknowledgement
- - yangtools, Implicit acknowledgement
-
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
-
-.. [1] Be sure to read the responsibilities of being a project lead under
- Leadership & Communication in the Requirements for Participation section
- of the release plan:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan#Requirements_for_Participation
-.. [2] Special needs include tools or configuration. Note that generally, the
- only available tools in CI are basic RHEL/CentOS linux images with Java.
- You should note and ask for anything beyond that here. Email
- helpdesk@opendaylight.org
+++ /dev/null
-========
-SNMP4SDN
-========
-
-1. Project PTL: Yi-Ling (Christine) Hsieh, ylhsieh@itri.org.tw, ChristineH
-
- - Yes, I have reviewed the PTL Requirements
-
-2. Project Contact: Yi-Ling (Christine) Hsieh, ylhsieh@itri.org.tw, ChristineH
-
-3. Test Contact: Yi-Ling (Christine) Hsieh, ylhsieh@itri.org.tw, ChristineH
-
-4. Documentation Contact: Yi-Ling (Christine) Hsieh, ylhsieh@itri.org.tw, ChristineH
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-7. Does your project have any special needs in CI Infrastructure [2]_? No
-
-8. Is your project release plan finalized? Yes
-
- - `Release plan <https://wiki.opendaylight.org/view/SNMP4SDN:Release_Plan_Oxygen>`_
-
-9. Do you have all APIs intended to be externally consumable listed?
-
- - Does each API have a useful short name? *Yes*
- - Are the Java interface and/or YANG files listed for each API? *Yes*
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? *Yes*
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? *Yes*
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Yes
-
-11. Will your project have top-level features not requiring system test? Yes
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? No
-
-
-.. [1] Be sure to read the responsibilities of being a project lead under
- Leadership & Communication in the Requirements for Participation section
- of the release plan:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan#Requirements_for_Participation
-.. [2] Special needs include tools or configuration. Note that generally, the
- only available tools in CI are basic RHEL/CentOS linux images with Java.
- You should note and ask for anything beyond that here. Email
- helpdesk@opendaylight.org
+++ /dev/null
-============
-SXP
-============
-
-1. Project PTL: Michal Rehak, lagosaurus.42@gmail.com, mirehak
-
-2. Project Contact: Martin Dindoffer, mdindoff@cisco.com, mdindoff
-
-3. Test Contact: Martin Dindoffer, mdindoff@cisco.com, mdindoff
-
-4. Documentation Contact: Martin Dindoffer, mdindoff@cisco.com, mdindoff
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-7. Does your project have any special needs in CI Infrastructure? No
-
-8. Is your project release plan finalized? Yes
-
- - `Release plan <https://wiki.opendaylight.org/view/SXP:Oxygen:Release_Plan>`_
-
-9. Do you have all APIs intended to be externally consumable listed?
-
- - Does each API have a useful short name? *Yes*
- - Are the Java interface and/or YANG files listed for each API? *Yes*
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? *Yes*
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? *Yes*
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Yes
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
+++ /dev/null
-====
-TSDR
-====
-
-1. Project PTL: YuLing Chen, yulingchen54@gmail.com, yuling_c
-
- - Yes, I have reviewed the PTL Requirements [1]_.
-
-2. Project Contact: Scott Melton, smelton2@uccs.edu
-
-3. Test Contact: YuLing Chen, yulingchen54@gmail.com, yuling_c
-
-4. Documentation Contact: Scott Melton, smelton2@uccs.edu
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-7. Does your project have any special needs in CI Infrastructure [2]_? No
-
-8. Is your project release plan finalized? Yes
-
- - `Release plan <https://wiki.opendaylight.org/view/TSDR:TSDR_Oxygen_Release_Plan>`_
-
-9. Do you have all APIs intended to be externally consumable listed?
-
- - Does each API have a useful short name? *Yes*
- - Are the Java interface and/or YANG files listed for each API? *Yes*
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? *Yes*
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? *Yes*
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects?
-
- - controller, Implicit acknowledgement
- - mdsal, Implicit acknowledgement
- - odlparent, Implicit acknowledgement
- - yangtools, Implicit acknowledgement
- - openflowplugin, Implicit acknowledgement
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
-
-.. [1] Be sure to read the responsibilities of being a project lead under
- Leadership & Communication in the Requirements for Participation section
- of the release plan:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan#Requirements_for_Participation
-.. [2] Special needs include tools or configuration. Note that generally, the
- only available tools in CI are basic RHEL/CentOS linux images with Java.
- You should note and ask for anything beyond that here. Email
- helpdesk@opendaylight.org
+++ /dev/null
-======
-Unimgr
-======
-
-1. Project PTL: Donald Hunter, donaldh@cisco.com, donaldh
-
- - Yes, I have reviewed the PTL Requirements [1]_.
-
-2. Project Contact: Donald Hunter, donaldh@cisco.com, donaldh
-
-3. Test Contact: Bartosz Michalik, bartosz.michalik@amartus.com
-
-4. Documentation Contact: Charles Eckel, eckelcu@cisco.com
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-7. Does your project have any special needs in CI Infrastructure [2]_? No
-
-8. Is your project release plan finalized? No
-
-9. Do you have all APIs intended to be externally consumable listed?
-
- - Does each API have a useful short name? *Yes*
- - Are the Java interface and/or YANG files listed for each API? *Yes*
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? *Yes*
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? *Yes*
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects?
-
- - dlux, not acknowledged
- - genius, not acknowledged
- - l2switch, not acknowledged
- - netvirt, not acknowledged
- - ovsdb, not acknowledged
- - vpnservice, not acknowledged
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
-
-
-.. [1] Be sure to read the responsibilities of being a project lead under
- Leadership & Communication in the Requirements for Participation section
- of the release plan:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan#Requirements_for_Participation
-.. [2] Special needs include tools or configuration. Note that generally, the
- only available tools in CI are basic RHEL/CentOS linux images with Java.
- You should note and ask for anything beyond that here. Email
- helpdesk@opendaylight.org
+++ /dev/null
-===
-USC
-===
-
-1. Project PTL: A H, an.ho@huawei.com, anipbu
-
- - Yes, I have reviewed the PTL Requirements.
-
-2. Project Contact: A H, an.ho@huawei.com, anipbu
-
-3. Test Contact: A H, an.ho@huawei.com, anipbu
-
-4. Documentation Contact: A H, an.ho@huawei.com, anipbu
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No
-
-7. Does your project have any special needs in CI Infrastructure? No
-
-8. Is your project release plan finalized? Yes
-
- - `Release plan <https://wiki.opendaylight.org/view/USC:Oxygen:Release_Plan>`_
-
-9. Do you have all APIs intended to be externally consumable listed?
-
- - Does each API have a useful short name? *Yes*
- - Are the Java interface and/or YANG files listed for each API? *Yes*
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? *Yes*
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? *Yes*
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Yes
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
+++ /dev/null
-===
-VTN
-===
-
-1. Project PTL: Hideyuki Tai, h-tai@cd.jp.nec.com, hideyuki
-
- - Yes, I have reviewed the PTL Requirements [1]_.
-
-2. Project Contact: Venkatrangan Govindarajan, venkatrangang@hcl.com, gvrangan
-
-3. Test Contact: Venkatrangan Govindarajan, venkatrangang@hcl.com, gvrangan
-
-4. Documentation Contact: Venkatrangan Govindarajan, venkatrangang@hcl.com, gvrangan
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-7. Does your project have any special needs in CI Infrastructure [2]_? No
-
-8. Is your project release plan finalized? Yes
-
- - `Release plan <https://wiki.opendaylight.org/view/VTN:Oxygen_Release_Plan>`_
-
-9. Do you have all APIs intended to be externally consumable listed?
-
- - Does each API have a useful short name? - *Yes*
- - Are the Java interface and/or YANG files listed for each API? - *Yes*
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? - *No*
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? - *No*
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Yes
-
-11. Will your project have top-level features not requiring system test? No
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
-
-.. [1] Be sure to read the responsibilities of being a project lead under
- Leadership & Communication in the Requirements for Participation section
- of the release plan:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan#Requirements_for_Participation
-.. [2] Special needs include tools or configuration. Note that generally, the
- only available tools in CI are basic RHEL/CentOS linux images with Java.
- You should note and ask for anything beyond that here. Email
- helpdesk@opendaylight.org
+++ /dev/null
-==========
-YANG Tools
-==========
-
-1. Project PTL: Robert Varga, robert.varga@pantheon.tech, rovarga
-
- - Yes, I have reviewed the PTL Requirements
-
-2. Project Contact: Robert Varga, robert.varga@pantheon.tech, rovarga
-
-3. Test Contact: Vratko Polak, vrpolak@cisco.com, vrpolak
-
-4. Documentation Contact: Robert Varga, robert.varga@pantheon.tech, rovarga
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? No
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? Yes
-
-7. Does your project have any special needs in CI Infrastructure? No
-
-8. Is your project release plan finalized? No
-
- - We are in churn to get the 2.0.0 release out. Since we are waiting
- for odlparent-3.0.0, we are still cleaning up APIs.
-
-9. Do you have all APIs intended to be externally consumable listed? Yes
-
- - Does each API have a useful short name? Yes
- - Are the Java interface and/or YANG files listed for each API? Yes
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? Yes
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? Yes
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? Yes
-
-11. Will your project have top-level features not requiring system test? Yes
-
- - Experimental features, waiver TBD
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? Yes
+++ /dev/null
-============
-Project Name
-============
-
-1. Project PTL:
-
- - name
- - email
- - IRC handle
- - I have reviewed the PTL Requirements [1]_
-
-2. Project Contact:
-
- - name
- - email
- - IRC handle
-
-3. Test Contact:
-
- - name
- - email
- - IRC handle
-
-4. Documentation Contact
-
- - name
- - email
- - IRC handle
-
-5. Does your project have any updates on any previously-incomplete items from
- prior milestone readouts? (Yes/No)
-
- - (If yes, list updates)
-
-6. Were project-specific deliverables planned for this milestone delivered
- successfully? (No Deliverables/Yes/No)
-
- - (If no, list incomplete deliverables)
-
-7. Does your project have any special needs in CI Infrastructure [2]_? (Yes/No)
-
- - (If yes, link to helpdesk ticket number)
-
-8. Is your project release plan finalized? (Yes/No)
-
- - (If yes, link to final release plan wiki page)
- - (If no, ETA to finalize release plan)
-
-9. Do you have all APIs intended to be externally consumable listed? (Yes/No/Not Applicable)
-
- - Does each API have a useful short name? (Yes/No)
- - Are the Java interface and/or YANG files listed for each API? (Yes/No)
- - Are they labeled as tentative, provisional, or stable as appropriate for
- each API? (Yes/No)
- - Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? (Yes/No)
-
-10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? (Yes/No)
-
- - (List of all project dependencies and if they have been acknowledged, unacknowledged)
-
-11. Will your project have top-level features not requiring system test?
- (Yes/No)
-
- - (If yes, link to system test waiver request email)
-
-12. Will your project use the OpenDaylight CI infrastructure for testing
- top-level features requiring system test? (Yes/No)
-
- - (If no, link to system test plan explaining why [3]_)
- - (If no, link to system test plan identifying external lab testing [4]_)
-
-**FOR NEW PROJECTS ONLY**
-
-A. Project Main Page: (wiki link)
-
- - Use Project Facts Template [5]_
-
-B. Have you completed the project checklist [6]_? (Yes/No)
-
- - (link to a merged patch in gerrit)
- - (link to a mail from your mailing list)
- - (link to a bug for your project; you can create a dummy one and close it if need be)
- - (link to an artifact published from your project in nexus)
- - (link to a sonar report)
- - (link to your root pom file)
-
-.. [1] Be sure to read the responsibilities of being a project lead under
- Leadership & Communication in the Requirements for Participation section
- of the release plan:
- https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan#Requirements_for_Participation
-.. [2] Special needs include tools or configuration. Note that generally, the
- only available tools in CI are basic RHEL/CentOS linux images with Java.
- You should note and ask for anything beyond that here. Email
- helpdesk@opendaylight.org
-.. [3] It is recommended to use the OpenDaylight CI infrastructure unless there
- is some HW or SW resource that cannot be installed there. Update the
- test plan with explanation on why your top-level features will not be
- using the OpenDaylight CI Infrastructure:
- https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template#Test_Infrastructure
-.. [4] Projects running system test in external Labs are required to report
- system test results in a timely fashion after release creations, e.g.,
- weekly, RC, and formal releases. Update the test plan with plans on
- testing in external lab:
- https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template#Test_Infrastructure
-.. [5] https://wiki.opendaylight.org/view/Template:Project_Facts
-.. [6] https://wiki.opendaylight.org/view/GettingStarted:Project_Main#New_Project_Checklist
+++ /dev/null
-===
-AAA
-===
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-None
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes/No
-
- - If you had Tentative APIs, have they been moved to Provisional or dropped?
- Yes
- - If any of your Tentative APIs were dropped, have you notified all projects
- that were expecting them?
- N/A
- - Also please list all dropped APIs.
- N/A
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? Yes
-
-3. Were there any project-specific deliverables planned for this milestone?
- No
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? Yes
-
- - `Features <https://git.opendaylight.org/gerrit/gitweb?p=aaa.git;a=blob_plain;f=features/aaa/features-aaa/pom.xml;hb=refs/heads/master>`_
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - **odl-aaa-api**
- - Provides generic AAA API constructs.
-
- - **odl-aaa-cert**
- - Enables an MD-SAL based certificate store for southbound protocol usage.
-
- - **odl-aaa-cli**
- - Installs a number of AAA specific Karaf CLI commands for administrative purposes.
-
- - **odl-aaa-encryption-service**
- - Provides a service to do basic encryption/decryption based on a set of common defaults.
-
- - **odl-aaa-shiro**
- - Enables AAA on all ODL RESTFUL interfaces.
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - One user/operator guide section per user-facing feature.
- - One developer guide per top-level feature.
- - An installation guide for any top-level features that require more than
- feature:install <feature-name> to install.
- - Release notes (mandatory) [2]_.
- - Optional tutorials and how-tos.
-
-2. Have you checked in a reStructuredText outline to the docs repository? No
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features? Yes
-
- - `Feature Test Report <https://jenkins.opendaylight.org/releng/view/aaa/job/aaa-csit-1node-authn-all-nitrogen/246/>`_
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? Yes
-
- - `System Test Report <https://jenkins.opendaylight.org/releng/view/aaa/job/aaa-csit-1node-authn-all-nitrogen/246/>`_
-
-3. Have you integrated odlparent 3 / yangtools 2? No
-
- - Incomplete. `Pending Patch <https://git.opendaylight.org/gerrit/#/c/64196/>`_
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone?
- No
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-====
-ALTO
-====
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes
-
- - If you had Tentative APIs, have they been moved to Provisional or dropped?
- N/A
-
- - If any of your Tentative APIs were dropped, have you notified all projects
- that were expecting them?
- N/A
-
- - Also please list all dropped APIs.
- N/A
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)?
- Yes
-
-3. Were there any project-specific deliverables planned for this milestone?
- No
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository?
- Yes
-
- - https://git.opendaylight.org/gerrit/gitweb?p=alto.git;a=blob;f=alto-release-features/features-alto/pom.xml;h=9b6d26050f06c3d508853c7ce005d4bd1c4b096b;hb=refs/heads/master
- - https://git.opendaylight.org/gerrit/gitweb?p=integration/distribution.git;a=blob;f=features/repos/index/pom.xml;h=d9dbcafaed73ad39695a25a06e4e8f0ceb79b904;hb=HEAD
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/release-notes/projects/alto.rst
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - User Guide(s).
- - Developer Guide(s).
- - Installation Guide(s).
- - Release notes (mandatory).
-
-2. Have you checked in a reStructuredText outline to the docs repository? Yes
-
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/alto-user-guide.rst;h=3093d9d546d2db987307a1fe0cb43daa9a5b4214;hb=HEAD
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features?
- Yes
-
- - https://jenkins.opendaylight.org/releng/view/alto/
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature?
- Yes
-
- - https://wiki.opendaylight.org/view/ALTO:_System_Test_Plan
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone?
- No
-
-2. Have you updated your project facts with the project type category?
- Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy?
- Yes
+++ /dev/null
-===========
-BGP LS PCEP
-===========
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes/No
-
- - https://wiki.opendaylight.org/view/BGP_LS_PCEP:Oxygen_Release_Plan#Externally_Consumable_APIs
- - https://wiki.opendaylight.org/view/BGP_LS_PCEP:Oxygen_Release_Plan#Removed_APIs_and.2For_Functionality
-
-2. Are all your inter-project dependencies resolved?
-
- - Yes
-
-3. Were there any project-specific deliverables planned for this milestone?
-
- - No
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository?
-
- - Yes
- - https://git.opendaylight.org/gerrit/gitweb?p=bgpcep.git;a=blob;f=features/bgp/src/main/features/features.xml;h=0ac6b0b0a2286515900879ed374e5138b61a49e2;hb=refs/heads/master
- - https://git.opendaylight.org/gerrit/gitweb?p=bgpcep.git;a=blob;f=features/pcep/src/main/features/features.xml;h=0ac6b0b0a2286515900879ed374e5138b61a49e2;hb=refs/heads/master
- - https://git.opendaylight.org/gerrit/gitweb?p=bgpcep.git;a=blob;f=features/bmp/src/main/features/features.xml;h=0ac6b0b0a2286515900879ed374e5138b61a49e2;hb=refs/heads/master
- - https://git.opendaylight.org/gerrit/gitweb?p=bgpcep.git;a=blob;f=features/rsvp/src/main/features/features.xml;h=0ac6b0b0a2286515900879ed374e5138b61a49e2;hb=refs/heads/master
- - https://git.opendaylight.org/gerrit/gitweb?p=bgpcep.git;a=blob;f=features/extras/src/main/features/features.xml;h=0ac6b0b0a2286515900879ed374e5138b61a49e2;hb=refs/heads/master
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - odl-bgpcep-bgp
- - odl-bgpcep-bmp
- - odl-bgpcep-pcep
- - odl-bgpcep-rsvp
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - developer guide
- - user guide
- - Release notes (mandatory).
-
-2. Have you checked in a reStructuredText outline to the docs repository?
-
- - Yes.
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/bgp-developer-guide.rst;h=0e5df8030a53fc22aeb044982758f362271d91b3;hb=refs/heads/master
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/bgp-monitoring-protocol-developer-guide.rst;h=d83bbc7dce561e9ac6319cadba0a1460003d9641;hb=refs/heads/master
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/pcep-developer-guide.rst;h=d1b48bfbfb2b91b1002e6fff99cb9360490366ea;hb=refs/heads/master
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/bgp-user-guide.rst;h=307de691444779efdeda065d9f5e98791ef1bfc8;hb=refs/heads/master
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/bgp-monitoring-protocol-user-guide.rst;h=5153494111add81a13c3582d56d240ce782e63ec;hb=refs/heads/master
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/pcep-user-guide.rst;h=8cba92ecc27a7696656486b85649c4f740f8f6f9;hb=refs/heads/master
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features?
-
- - Yes.
- - https://jenkins.opendaylight.org/releng/view/bgpcep/job/bgpcep-csit-1node-periodic-bgp-ingest-mixed-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/bgpcep/job/bgpcep-csit-1node-periodic-bgp-ingest-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/bgpcep/job/bgpcep-csit-1node-periodic-throughpcep-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/bgpcep/job/bgpcep-csit-1node-userfeatures-all-oxygen/
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature?
-
- - Yes
- - https://wiki.opendaylight.org/view/BGP_LS_PCEP:Oxygen_Feature_Tests
-
-3. Have you integrated odlparent 3 / yangtools 2?
-
- - No
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone? No
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-====
-BIER
-====
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes/No
-
- - Yes,https://wiki.opendaylight.org/view/BIER:Oxygen:Release_Plan#Externally_Consumable_APIs
- - No dropped APIs
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? (Yes/No)
-
- - Yes
-
-3. Were there any project-specific deliverables planned for this milestone?
- Yes/No
-
- - No
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? (Yes/No)
-
- - Yes, https://git.opendaylight.org/gerrit/gitweb?p=integration/distribution.git;a=blob;f=features/repos/index/pom.xml
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/release-notes/projects/bier.rst
- - odl-bier-all
- - odl-bier-models
- - odl-bier-bierman
- - odl-bier-channel
- - odl-bier-service
- - odl-bier-te-pce
- - odl-bier-std-driver
- - odl-bier-adapter
- - odl-bier-oam
- - odl-bier-app
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - developer guide
- - user guide
- - Release notes (mandatory).
-
-2. Have you checked in a reStructuredText outline to the docs repository? (Yes/No)
-
- - Yes
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/bier-user-guide.rst
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/bier-developer-guide.rst
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features?
- (Yes/No)
-
- - Yes, https://jenkins.opendaylight.org/releng/view/bier/job/bier-csit-1node-basic-all-oxygen/
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? (Yes/No)
-
- - Yes, https://git.opendaylight.org/gerrit/gitweb?p=integration/test.git;a=blob;f=csit/testplans/bier-basic.txt
-
-3. Have you integrated odlparent 3 / yangtools 2? (Yes/No/NA)
-
- - No
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone?
- (Yes/No)
-
- - No
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-===
-COE
-===
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes/No
-
- Yes. No tentative API.
-
- - If you had Tentative APIs, have they been moved to Provisional or dropped?
-
- N/A
-
- - If any of your Tentative APIs were dropped, have you notified all projects
- that were expecting them? (Yes/No) <link to e-mail>
-
- N/A
-
- - Also please list all dropped APIs.
-
- N/A
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? (Yes/No)
-
- Yes.
-
-3. Were there any project-specific deliverables planned for this milestone?
- Yes/No
-
- No.
-
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? (Yes/No)
-
- Yes
-
- - https://git.opendaylight.org/gerrit/gitweb?p=integration/distribution.git;a=blob;f=features/repos/index/pom.xml
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - odl-coe: https://git.opendaylight.org/gerrit/gitweb?p=coe.git;a=blob;f=features/odl-coe/pom.xml
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - Coe Design Document
- https://wiki.opendaylight.org/view/COE:Design_doc
- - An installation guide for any top-level features that require more than
- feature:install <feature-name> to install.
- N/A as this is covered by service provider, e.g. netvirt
- - Release notes (mandatory) [2]_.
- COE will be doing a release only in Oxygen, will be adding that towards the end
- - Optional tutorials and how-tos.
- N/A
-
-2. Have you checked in a reStructuredText outline to the docs repository? (Yes/No)
-
- Yes
-
- - https://git.opendaylight.org/gerrit/gitweb?p=coe.git;a=tree;f=docs
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features?
- (Yes/No)
-
- N/A (System test will be covered by the service provider which is going to be Netvirt)
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? (Yes/No)
-
- N/A as 1.
-
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone?
- (Yes/No)
-
- No.
-
-2. Have you updated your project facts with the project type category? (Yes/No)
-
- Yes.
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? (Yes/No)
-
- Yes.
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-============
-controller
-============
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? Yes
-
-3. Were there any project-specific deliverables planned for this milestone?
- No
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? Yes
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/release-notes/projects/controller.rst
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - User guide.
- - Developer guide.
- - Release notes (mandatory) [2]_.
-
-2. Have you checked in a reStructuredText outline to the docs repository? No
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features?
- Yes
-
- - https://jenkins.opendaylight.org/releng/view/controller/
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? Yes
-
-3. Have you integrated odlparent 3 / yangtools 2? Yes
-
- - https://git.opendaylight.org/gerrit/#/c/64175/
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone?
- No
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-======
-DAEXIM
-======
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-
-N/A. No prior incomplete item.
-
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes/No
-
- Yes
-
- - If you had Tentative APIs, have they been moved to Provisional or dropped?
- (Yes/No) <link to release plan>
-
- No. No provisional API.
-
- - If any of your Tentative APIs were dropped, have you notified all projects
- that were expecting them? (Yes/No) <link to e-mail>
-
- N/A
-
- - Also please list all dropped APIs.
-
- N/A
-
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? (Yes/No)
-
- Yes.
-
- - (If no, please list the features you were expecting that have not been delivered)
-
- N/A
-
- - (The respective project [1]_ you were expecting to receive them from)
-
- N/A
-
-
-3. Were there any project-specific deliverables planned for this milestone?
- Yes/No
-
- No planned deliverables.
-
- - (If so, were they delivered? Yes/No)
-
- N/A
-
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? (Yes/No)
-
- No new features. All features added in prior release.
-
- - Please provide link to gerrit patch
-
- N/A
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
- odl-daexim, odl-daexim-all
-
- - For top-level and user-facing features, please provide a one-sentence
- description a developer and/or user would find helpful.
-
- -- odl-daexim: This is the core feature.
- -- old-daexim-all: This contains the core and supporting features, like restconf.
-
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - One user/operator guide section per user-facing feature.
- - One developer guide per top-level feature.
- - An installation guide for any top-level features that require more than
- feature:install <feature-name> to install.
- - Release notes (mandatory) [2]_.
- - Optional tutorials and how-tos.
-
- User and developer guides already exist. No changes needed.
-
-
-2. Have you checked in a reStructuredText outline to the docs repository? (Yes/No)
-
- Yes. Added in prior release.
-
- - Please provide link to gerrit patch
-
- N/A
-
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features?
- (Yes/No)
- - (If yes, link to test report)
- - (If no, why?)
-
- Yes.
- https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/daexim-csit-1node-basic-only-nitrogen/
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? (Yes/No)
-
- - (If yes, link to test plans)
- - (If no, why?)
-
- Yes.
- https://github.com/opendaylight/releng-builder/blob/master/jjb/daexim/daexim-csit-basic.yaml
-
-
-3. Have you integrated odlparent 3 / yangtools 2? (Yes/No/NA)
-
- - (If yes, link to gerrit patch)
-
- No
-
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone?
- (Yes/No)
- No
-
- - (If so, were they delivered? Yes/No )
-
- N/A
-
-
-2. Have you updated your project facts with the project type category? (Yes/No)
- Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? (Yes/No)
- Yes.
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-========================
-Integration Distribution
-========================
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes
-
- - If you had Tentative APIs, have they been moved to Provisional or dropped? Yes
- - If any of your Tentative APIs were dropped, have you notified all projects
- that were expecting them? No project expected API change.
- - Also please list all dropped APIs. Dropped features:
- odl-integration-compatible-with-1node, odl-integration-compatible-with-3node
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? Yes
-
-3. Were there any project-specific deliverables planned for this milestone?
- No
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? Yes
-
- - ` Features <https://git.opendaylight.org/gerrit/gitweb?p=integration/distribution.git;a=tree;f=features/singles;h=57fd26cc25c76b7efa484bd7c6b0cbce81db097c;hb=HEAD>`_
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- * **odl-distribution-version**: Feature to retrieve distribution version
- * **odl-integration-compatible-with-all**: Feature containing compatible user-facing features (used for test)
- * **odl-integration-all**: Feature containing all projects user-facing features (used for test)
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- * **User Guide for distribution version:**
-
- * :doc:`../../../user-guide/distribution-version-user-guide`
-
- * **Developer Guide for distribution version:**
-
- * :doc:`../../../developer-guide/distribution-version`
-
- * **Developer Guide for distribution test features:**
-
- * :doc:`../../../developer-guide/distribution-test-features`
-
- * **Distribution scripts:**
-
- * :doc:`../../../getting-started-guide/common-features/clustering`
- * :doc:`../../../getting-started-guide/common-features/persistence_and_backup`
-
- * Release notes
-
-2. Have you checked in a reStructuredText outline to the docs repository? No
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features?
- Yes
-
- - ` CSIT Tests <https://jenkins.opendaylight.org/releng/view/distribution/>`_
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? Yes
-
- - ` Test Plans <https://wiki.opendaylight.org/view/Integration/Distribution/Oxygen_Feature_Tests>`_
-
-3. Have you integrated odlparent 3 / yangtools 2? No
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone?
- No
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-====
-DLUX
-====
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes/No
-
- - If you had Tentative APIs, have they been moved to Provisional or dropped?
- (NA)
- - If any of your Tentative APIs were dropped, have you notified all projects
- that were expecting them? (NA)
- - Also please list all dropped APIs. (NA)
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? (NA)
-
-3. Were there any project-specific deliverables planned for this milestone? (No)
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? (Yes)
-
- - https://git.opendaylight.org/gerrit/gitweb?p=integration/distribution.git;a=blob;f=features/repos/index/pom.xml
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - odl-dlux-core
- Core providing basic layout, AAA etc functionality.
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - One developer guide per top-level feature.
- - Release notes (mandatory)
-
-2. Have you checked in a reStructuredText outline to the docs repository? (No)
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features? (No)
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? (No)
-
-3. Have you integrated odlparent 3 / yangtools 2? (Yes)
-
- - https://git.opendaylight.org/gerrit/#/c/66475/
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone? (No)
-
-2. Have you updated your project facts with the project type category? (Yes)
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy? (Yes)
-
+++ /dev/null
-========
-DLUXApps
-========
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes/No
-
- - If you had Tentative APIs, have they been moved to Provisional or dropped?
- (NA)
- - If any of your Tentative APIs were dropped, have you notified all projects
- that were expecting them? (NA)
- - Also please list all dropped APIs. (NA)
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? (NA)
-
-3. Were there any project-specific deliverables planned for this milestone? (No)
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? (Yes)
-
- - https://git.opendaylight.org/gerrit/gitweb?p=integration/distribution.git;a=blob;f=features/repos/index/pom.xml
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - odl-dluxapps-nodes
- Application displays list of nodes in openflow (flow:1) topology.
-
- - odl-dluxapps-topology
- Basic topology application. Displays nodes and links from openflow (flow:1) topology.
-
- - odl-dluxapps-yangman
- GUI for data manipulation in controller. Generates forms based on loaded Yang models.
- User can interact with controller without knowledge of Yang models, test them, etc. Replacement of YangUI app.
-
- - odl-dluxapps-yangui
- Previous version of YangUI. Will be removed in next release.
-
- - odl-dluxapps-yangvisualizer
- Topology-like visualization of Yang models loaded in controller.
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - One developer guide per top-level feature.
- - Release notes (mandatory)
-
-2. Have you checked in a reStructuredText outline to the docs repository? (No)
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features? (Yes)
-
- - https://jenkins.opendaylight.org/releng/view/dluxapps/
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? (No)
-
-3. Have you integrated odlparent 3 / yangtools 2? (Yes)
-
- - https://git.opendaylight.org/gerrit/#/c/66491/
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone? (No)
-
-2. Have you updated your project facts with the project type category? (Yes)
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy? (Yes)
-
+++ /dev/null
-====
-eman
-====
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts. None
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes
-
- - no tentative or dropped APIs
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? Yes
-
-
-3. Were there any project-specific deliverables planned for this milestone?
- No
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? Yes
-
- - No change from previous release
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- * ``eman-api`` Exposes energy management Informatin Model through REST APIs
- * ``eman-ui`` Adds support for DLUX.
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - docs/developer-guide/eman-developer-guide
- - docs/user-guide/eman-user-guide
- - docs/release-notes/eman
-
-2. Have you checked in a reStructuredText outline to the docs repository? No
-
- - Please provide link to gerrit patch
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features?
- Yes
-
- - https://jenkins.opendaylight.org/releng/view/eman/job/eman-distribution-check-oxygen/
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? No
-
- - No new features in this release, so no additional testing in needed
-
-3. Have you integrated odlparent 3 / yangtools 2? Yes
-
- - https://git.opendaylight.org/gerrit/#/c/66468/
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone?
- No
-
-
-2. Have you updated your project facts with the project type category? No
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-====
-FaaS
-====
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts. None
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? Yes
-
-3. Were there any project-specific deliverables planned for this milestone?
- No deliverables
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? Yes
-
- - https://git.opendaylight.org/gerrit/gitweb?p=integration/distribution.git;a=blob;f=features/repos/index/pom.xml;
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/release-notes/projects/faas.rst;
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - User Guide, Developer Guide
-
-2. Have you checked in a reStructuredText outline to the docs repository? Yes
-
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/fabric-as-a-service.rst;
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/fabric-as-a-service.rst;
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features? No
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? Yes
-
- - https://wiki.opendaylight.org/view/FaaS:SystemTestPlan
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone? No deliverables
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-======
-Genius
-======
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts. NA
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes
-
- Updates to mdsalutil-api module:
-
- - Following utility classes are removed:
-
- - ClusteringUtils
- - EntityOwnerUtils
-
- - Above utility classes are replaced by following new class:
-
- - EntityOwnershipUtils
-
- Updates to ITM api:
-
- - Additional new RPCs will be added by ITM scale improvements:
-
- - itm-rpc:get-egress-action
- - itm-rpc:set-bfd-enable-on-tunnel
-
- - Link to gerrit review for spec:
-
- - https://git.opendaylight.org/gerrit/#/c/65809/
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? Yes
-
-3. Were there any project-specific deliverables planned for this milestone? No
-
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? Yes
-
- - https://git.opendaylight.org/gerrit/gitweb?p=genius.git;a=blob_plain;f=features/genius-features/pom.xml
- - https://git.opendaylight.org/gerrit/gitweb?p=integration/distribution.git;a=blob;f=features/repos/index/pom.xml;h=d9dbcafaed73ad39695a25a06e4e8f0ceb79b904;hb=HEAD
-
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- * **odl-genius** : This feature provides all functionalities provided by
- genius modules, including interface manager, tunnel manager, resource manager
- and ID manager and MDSAL Utils. It includes Genius APIs and implementation.
-
- * **odl-genius-rest** : This feature includes RESTCONF with 'odl-genius'
- feature.
-
- * **odl-genius-api** : This feature includes API for all the functionalities
- provided by Genius.
-
- * **odl-genius-fcaps-application** : includes Genius FCAPS application.
-
- * **odl-genius-fcaps-framework** : includes Genius FCAPS Framework.
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - One user/operator guide section per user-facing feature.
-
- - https://wiki.opendaylight.org/view/Genius_:_An_Overview
- - https://wiki.opendaylight.org/view/Genius:_User_Guide
- - One developer guide per top-level feature.
-
- - http://docs.opendaylight.org/en/latest/submodules/genius/docs/index.html
-
- - An installation guide for any top-level features that require more than
- feature:install <feature-name> to install. --N/A
-
- - Release notes (mandatory) [2]_.
-
- - Optional tutorials and how-tos.
-
-2. Have you checked in a reStructuredText outline to the docs repository? Yes
-
- - Link to gerrit patch:
-
- - https://git.opendaylight.org/gerrit/#/c/53072/
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features? Yes
-
- - https://jenkins.opendaylight.org/releng/view/genius/
-
- - Link to test report:
-
- - https://jenkins.opendaylight.org/releng/view/genius/job/genius-csit-1node-upstream-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/genius/job/genius-csit-3node-upstream-all-oxygen/
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? Yes
-
- - Link to test plans:
-
- - https://wiki.opendaylight.org/view/Genius:test_plan
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone? No
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
-
+++ /dev/null
-================
-GROUPBASEDPOLICY
-================
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes
-
- - If you had Tentative APIs, have they been moved to Provisional or dropped?
- N/A
- - If any of your Tentative APIs were dropped, have you notified all projects
- that were expecting them? N/A
- - Also please list all dropped APIs.
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? N/A
-
-3. Were there any project-specific deliverables planned for this milestone?
- No
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? Yes
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - see list of external APIs here:
- https://wiki.opendaylight.org/view/Group_Based_Policy_(GBP)/Releases/Oxygen/Release_plan#Externally_Consumable_APIs.
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - One user/operator guide section per user-facing feature.
- - Release notes (mandatory).
-
-2. Have you checked in a reStructuredText outline to the docs repository? No
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features?
- Yes
-
- - https://jenkins.opendaylight.org/releng/view/groupbasedpolicy/job/groupbasedpolicy-csit-1node-3-node-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/groupbasedpolicy/job/groupbasedpolicy-csit-1node-6node-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/groupbasedpolicy/job/groupbasedpolicy-csit-3node-clustering-all-oxygen/
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? No
-
- - no stable features yet
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone?
- No
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-=============
-HONEYCOMB/VBD
-=============
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes
-
- - If you had Tentative APIs, have they been moved to Provisional or dropped?
- N/A
- - If any of your Tentative APIs were dropped, have you notified all projects
- that were expecting them? N/A
- - Also please list all dropped APIs.
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? N/A
-
-3. Were there any project-specific deliverables planned for this milestone?
- No
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? Yes
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - see list of external APIs here:
- https://wiki.opendaylight.org/view/Honeycomb/VBD/API
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - Release notes (mandatory).
- - Optional tutorials and how-tos.
-
-2. Have you checked in a reStructuredText outline to the docs repository? No
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features?
- No
-
- - all marked as experimental
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? No
-
- - no stable features yet
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone?
- No
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-==========
-InfraUtils
-==========
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? Yes
-
-3. Were there any project-specific deliverables planned for this milestone? No
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? Yes
-
- - https://git.opendaylight.org/gerrit/gitweb?p=integration/distribution.git;a=blob;f=features/repos/index/pom.xml
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/release-notes/projects/infrautils.rst
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - Developer Guide, JavaDocs
-
-2. Have you checked in a reStructuredText outline to the docs repository? (Yes/No)
-
- - https://git.opendaylight.org/gerrit/gitweb?p=infrautils.git;a=tree;f=docs
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features? N/A
-
- - Covered by application CSITs
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? N/A
-
-3. Have you integrated odlparent 3 / yangtools 2? No
-
- - (If yes, link to gerrit patch)
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone? No
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-========
-JSON-RPC
-========
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-
-N/A. No prior incomplete item.
-
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes/No
-
- Yes
-
- - If you had Tentative APIs, have they been moved to Provisional or dropped?
- (Yes/No) <link to release plan>
-
- No. No provisional API.
-
- - If any of your Tentative APIs were dropped, have you notified all projects
- that were expecting them? (Yes/No) <link to e-mail>
-
- N/A
-
- - Also please list all dropped APIs.
-
- N/A
-
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? (Yes/No)
-
- No.
-
- - (If no, please list the features you were expecting that have not been delivered)
-
- Awaiting completion of ODL Parent and yangtools migration in mdsal and other projects -
- gerrit: https://git.opendaylight.org/gerrit/#/c/66536/
- Once this is merged we will have everything we need.
-
- - (The respective project [1]_ you were expecting to receive them from)
-
- N/A
-
-
-3. Were there any project-specific deliverables planned for this milestone?
- Yes/No
-
- No planned deliverables.
-
- - (If so, were they delivered? Yes/No)
-
- N/A
-
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? (Yes/No)
-
- No new features. All features added in prior release.
-
- - Please provide link to gerrit patch
-
- N/A
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
- odl-daexim, odl-daexim-all
-
- - For top-level and user-facing features, please provide a one-sentence
- description a developer and/or user would find helpful.
-
- -- odl-jsonrpc: This is the core feature.
-
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - One user/operator guide section per user-facing feature.
- - One developer guide per top-level feature.
- - An installation guide for any top-level features that require more than
- feature:install <feature-name> to install.
- - Release notes (mandatory) [2]_.
- - Optional tutorials and how-tos.
-
- User and developer guides already exist. No changes needed.
-
-
-2. Have you checked in a reStructuredText outline to the docs repository? (Yes/No)
-
- No.
-
- - Will provide it by M3
-
- N/A
-
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features?
- (Yes/No)
- - (If yes, link to test report)
- - (If no, why?)
-
- Yes.
- https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/jsonrpc-csit-1node-basic-only-nitrogen/
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? (Yes/No)
-
- - (If yes, link to test plans)
- - (If no, why?)
-
- Yes.
- https://github.com/opendaylight/releng-builder/blob/master/jjb/jsonrpc/jsonrpc-csit-basic.yaml
-
-
-3. Have you integrated odlparent 3 / yangtools 2? (Yes/No/NA)
-
- - (If yes, link to gerrit patch)
-
- Awaiting dependencies before merge: https://git.opendaylight.org/gerrit/#/c/66536/
-
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone?
- (Yes/No)
- No
-
- - (If so, were they delivered? Yes/No )
-
- N/A
-
-
-2. Have you updated your project facts with the project type category? (Yes/No)
- Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? (Yes/No)
- Yes.
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-========
-l2switch
-========
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: **Yes, available in documentation. No change from previous releases.**
-
- - If you had Tentative APIs, have they been moved to Provisional or dropped?
- **N/A**
- - If any of your Tentative APIs were dropped, have you notified all projects
- that were expecting them? **N/A**
- - Also please list all dropped APIs.
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? **Yes**
-
-3. Were there any project-specific deliverables planned for this milestone? **No**
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? **Yes**
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- :odl-l2switch-packethandler: Decodes the packets coming to the controller
- and dispatches them to the other modules
-
- :odl-l2switch-loopremover: Runs STP and marks NodeConnectors as forwarding
- or blocking in the node inventory
-
- :odl-l2switch-arphandler: Responds to incoming ARP requests with learned
- addresses. In proactive-flood mode, floods traffic to all ports.
-
- :odl-l2switch-addresstracker: Observes IPv4, IPv6, and ARP traffic incoming
- via packethandler. Observations are written into the datastore for consumption
-
- :odl-l2switch-hosttracker: Translates address observations from the network
- (via addresstracker) into Hosts in the datastore
-
- :odl-l2switch-switch: Installs bi-directional MAC to MAC flows based on
- incoming ARP traffic
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - **User guide** http://docs.opendaylight.org/en/latest/user-guide/l2switch-user-guide.html
- - **Developer guide**, sections per feature http://docs.opendaylight.org/en/latest/developer-guide/l2switch-developer-guide.html
- - **Release notes** (mandatory) [2]_.
-
-2. Have you checked in a reStructuredText outline to the docs repository? **No**
-
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features?
- **Yes**
-
- - https://jenkins.opendaylight.org/releng/view/l2switch/job/l2switch-csit-1node-switch-all-oxygen/
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? **No**
-
- - (If no, why?) **This project is in maintenance mode, and is used mostly as an introductory project to ODL. We don't consider any features as stable. For each top-level feature we maintain a CSIT test suite, but no test plan template as such**
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone?
- **No**
-
-2. Have you updated your project facts with the project type category? **Yes**
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? **Yes**
-
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-=================
-LISP Flow Mapping
-=================
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-None
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes
-
- - If you had Tentative APIs, have they been moved to Provisional or dropped?
-
- - NA https://wiki.opendaylight.org/view/OpenDaylight_Lisp_Flow_Mapping:Oxygen_Release_Plan
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? No new dependencies
-
-3. Were there any project-specific deliverables planned for this milestone?
- No
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? No
-
- - In progress
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - **odl-lispflowmapping-msmr**: This is the core feature that provides the Mapping
- Services and include the LISP southbound plugin feature as well.
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - User Guide
- - Release Notes
-
-2. Have you checked in a reStructuredText outline to the docs repository? Yes
-
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/lisp-flow-mapping-user-guide.rst;h=db9419246f3e707f23c48d6ed965f11de7911c48;hb=HEAD
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features? Yes
-
- - https://jenkins.opendaylight.org/releng/view/lispflowmapping/job/lispflowmapping-csit-1node-msmr-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/lispflowmapping/job/lispflowmapping-csit-1node-performance-only-oxygen/
- - https://jenkins.opendaylight.org/releng/view/lispflowmapping/job/lispflowmapping-csit-3node-msmr-all-oxygen/
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? Yes
-
- - https://wiki.opendaylight.org/view/OpenDaylight_Lisp_Flow_Mapping:Oxygen:All_Integration_System_Test
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone?
- No
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-======
-MD-SAL
-======
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes
-
- - If you had Tentative APIs, have they been moved to Provisional or dropped? No
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? Yes
-
-3. Were there any project-specific deliverables planned for this milestone?
- Yes
-
- - If so, were they delivered? Yes
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? Yes
-
- - Existing feature
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- * **odl-triemap**: Ctrie-based java.util.Map implementation
- * **odl-yangtools-codec**: YANG data XML and JSON codecs
- * **odl-yangtools-common**: Common YANG constants and concepts
- * **odl-yangtools-data-api**: YANG data instance and transformation APIs
- * **odl-yangtools-data**: YANG data instance reference implementation
- * **odl-yangtools-export**: YANG metamodel encoding utilities
- * **odl-yangtools-parser-api**: YANG metamodel and parser APIs
- * **odl-yangtools-parser**: YANG/YIN RFC6020/RFC7950 parser and compiler
- * **odl-yangtools-util**: Core concepts and utilities
- * **odl-yangtools-xpath**: YANG data instance XPath support
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- * **Release notes**
-
- * :doc:`../../../release-notes/projects/mdsal`
-
-2. Have you checked in a reStructuredText outline to the docs repository? Yes
-
- - https://git.opendaylight.org/gerrit/66837
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features?
- Yes
-
- - ` CSIT Tests <https://jenkins.opendaylight.org/releng/view/mdsal/job/mdsal-csit-1node-periodic-bindingv1-only-oxygen/>`_
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? (Yes/No)
-
- - No, test plan is expected at M4.
-
-3. Have you integrated odlparent 3 / yangtools 2? (Yes/No/NA)
-
- - Yes, https://git.opendaylight.org/gerrit/65892.
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone?
- Yes.
-
- - If so, were they delivered? Yes.
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-====
-NEMO
-====
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? Yes
-
-3. Were there any project-specific deliverables planned for this milestone?
- No deliverables
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? Yes
-
- - https://git.opendaylight.org/gerrit/gitweb?p=integration/distribution.git;a=blob;f=features/repos/index/pom.xml;
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/release-notes/projects/nemo.rst;
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - User Guide, Developer Guide, Tutorials
-
-2. Have you checked in a reStructuredText outline to the docs repository? Yes
-
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/nemo-user-guide.rst;
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/nemo-developer-guide.rst;
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features? Yes
-
- - https://jenkins.opendaylight.org/releng/view/nemo/
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? Yes
-
- - https://wiki.opendaylight.org/view/NEMO:Integration_Test
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone? No deliverables
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-=======
-Netconf
-=======
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? Yes
-
-3. Were there any project-specific deliverables planned for this milestone?
- No
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? Yes
-
- - https://git.opendaylight.org/gerrit/gitweb?p=integration/distribution.git;a=blob;f=features/repos/index/pom.xml
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/release-notes/projects/netconf.rst
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - User/operator guide section per user-facing feature.
- - One developer guide per top-level feature.
- - Release notes (mandatory) [2]_.
-
-2. Have you checked in a reStructuredText outline to the docs repository? No
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features?
- Yes
-
- - https://jenkins.opendaylight.org/releng/view/netconf/
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? Yes
-
- - https://jenkins.opendaylight.org/releng/view/netconf/
-
-3. Have you integrated odlparent 3 / yangtools 2? Yes
-
- - https://git.opendaylight.org/gerrit/#/c/64202/
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone?
- No
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-=======
-NetVirt
-=======
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? Yes
-
-3. Were there any project-specific deliverables planned for this milestone? No
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? Yes
-
- - https://git.opendaylight.org/gerrit/gitweb?p=integration/distribution.git;a=blob;f=features/repos/index/pom.xml
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/release-notes/projects/netvirt.rst
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - User Guide, Developer Guide, Tutorials
-
-2. Have you checked in a reStructuredText outline to the docs repository? (Yes/No)
-
- - https://git.opendaylight.org/gerrit/gitweb?p=netvirt.git;a=tree;f=docs;h=5eba14dcaa5780e9b4b9052924b2c7f5df7eee0c;hb=HEAD
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features? Yes
-
- - https://jenkins.opendaylight.org/releng/view/netvirt-csit/
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? Yes
-
- - https://wiki.opendaylight.org/view/NetVirt:Integration_Test
-
-3. Have you integrated odlparent 3 / yangtools 2? No
-
- - (If yes, link to gerrit patch)
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone? No
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-==================
-Neutron Northbound
-==================
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes/No
-
- Yes. No tentative API.
-
- - If you had Tentative APIs, have they been moved to Provisional or dropped?
-
- N/A
-
- - If any of your Tentative APIs were dropped, have you notified all projects
- that were expecting them? (Yes/No) <link to e-mail>
-
- N/A
-
- - Also please list all dropped APIs.
-
- N/A
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? (Yes/No)
-
- Yes.
-
- - (If no, please list the features you were expecting that have not been delivered)
-
- N/A
-
- - (The respective project [1]_ you were expecting to receive them from)
-
- N/A
-
-3. Were there any project-specific deliverables planned for this milestone?
- Yes/No
-
- No.
-
- - (If so, were they delivered? Yes/No)
-
- N/A
-
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? (Yes/No)
-
- Yes
-
- - Please provide link to gerrit patch
-
- https://git.opendaylight.org/gerrit/#/c/58981/
-
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - For top-level and user-facing features, please provide a one-sentence
- description a developer and/or user would find helpful.
-
- - odl-neutron-service: Basic library for for openstack Neutron integration working with networking-odl
-
-
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- Yes. no updates from Carbon.
-
- - One user/operator guide section per user-facing feature.
- https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/neutron-service-user-guide.rst;hb=HEAD
- - One developer guide per top-level feature.
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/neutron-service-developer-guide.rst;hb=HEAD
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/neutron-northbound.rst;hb=HEAD
- - An installation guide for any top-level features that require more than
- feature:install <feature-name> to install.
- N/A as this is covered by openstack service provider, e.g. netvirt
- - Release notes (mandatory) [2]_.
- https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/release-notes/projects/neutron-northbound.rst;hb=HEAD
- - Optional tutorials and how-tos.
- N/A
-
-
-2. Have you checked in a reStructuredText outline to the docs repository? (Yes/No)
-
- Yes
-
- - Please provide link to gerrit patch
-
- https://git.opendaylight.org/gerrit/#/c/44169/
-
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features?
- (Yes/No)
-
- No
-
- - (If yes, link to test report)
- - (If no, why?)
-
- the project has requested system test weaver as before release.
- https://lists.opendaylight.org/pipermail/release/2017-October/012703.html
- Basically system test is done by openstack service provider like netvirt and also
- openstack CI by networking-odl project.
- https://review.openstack.org/#/c/521692/
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? (Yes/No)
-
- N/A as 1.
-
- - (If yes, link to test plans)
- - (If no, why?)
-
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone?
- (Yes/No)
-
- No.
-
- - (If so, were they delivered? Yes/No )
-
- N/A
-
-2. Have you updated your project facts with the project type category? (Yes/No)
-
- Yes.
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? (Yes/No)
-
- Yes.
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-=====
-NIC
-=====
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-None
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes
-
- - If you had Tentative APIs, have they been moved to Provisional or dropped? No
-
- - If any of your Tentative APIs were dropped, have you notified all projects
- that were expecting them? No API dropped.
- - Also please list all dropped APIs. - None
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? Yes
-
-3. Were there any project-specific deliverables planned for this milestone? No (Mainly Bug Fixes)
-
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? Yes
-
- - `Existing Features <https://git.opendaylight.org/gerrit/gitweb?p=nic.git;a=shortlog;h=HEAD>`_
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - **Network Intent Composition (NIC)**:
-
- * **odl-nic-inent-common**: User should install this feature if they want to load the NIC project.
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- * **User Guide(s):**
-
- * :doc:`NIC User Guide <../../../user-guide/network-intent-composition-(nic)-user-guide>`
-
- * **Developer Guide(s):**
-
- * :doc:`NIC Developer Guide <../../../developer-guide/network-intent-composition-guide>`
-
- * Release notes
-
-2. Have you checked in a reStructuredText outline to the docs repository? No
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features? Yes
-
- - ` CSIT Tests <https://jenkins.opendaylight.org/releng/view/nic/>`_
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? No
-
- - Not done yet, will be available by M3
-
-3. Have you integrated odlparent 3 / yangtools 2? No
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone? Yes (Mostly add new test cases)
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-==========
-ODL Parent
-==========
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes
-
- - If you had Tentative APIs, have they been moved to Provisional or dropped?
- N/A
- - If any of your Tentative APIs were dropped, have you notified all projects
- that were expecting them? N/A
- - Also please list all dropped APIs.
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? N/A
-
-3. Were there any project-specific deliverables planned for this milestone?
- Yes
-
- - No, odlparent 3.0.0 is in preparation and should be ready by November 10
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? No
-
- - Gerrit patch in preparation
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - See the release plan:
- https://wiki.opendaylight.org/view/ODL_Parent:Oxygen_Release_Plan#Externally_Consumable_APIs
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - One developer guide per top-level feature.
- - Release notes (mandatory).
-
-2. Have you checked in a reStructuredText outline to the docs repository? No
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features?
- No
-
- - ODL Parent has a test waiver
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? No
-
- - See above
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone?
- Yes
-
- - See above
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy? Yes
+++ /dev/null
-=========
-OF-CONFIG
-=========
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes/No
-
- - Yes, https://wiki.opendaylight.org/view/OF-CONFIG:Oxygen:Release_Plan#Externally_Consumable_APIs
- - No dropped APIs
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? (Yes/No)
-
- - Yes
-
-3. Were there any project-specific deliverables planned for this milestone?
- Yes/No
-
- - No
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? (Yes/No)
-
- - Yes, https://git.opendaylight.org/gerrit/gitweb?p=integration/distribution.git;a=blob;f=features/repos/index/pom.xml
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/release-notes/projects/of-config.rst
- - odl-of-config-all
- - odl-of-config-southbound-rest
- - odl-of-config-southbound-all
- - odl-of-config-southbound-api
- - odl-of-config-southbound-ofconfigmodels
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - developer guide
- - user guide
- - Release notes (mandatory).
-
-2. Have you checked in a reStructuredText outline to the docs repository? (Yes/No)
-
- - Yes
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/of-config-user-guide.rst
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/of-config-developer-guide.rst
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features?
- (Yes/No)
-
- - Yes, https://jenkins.opendaylight.org/releng/view/of-config/job/of-config-csit-1node-basic-all-oxygen/
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? (Yes/No)
-
- - Yes, https://git.opendaylight.org/gerrit/gitweb?p=integration/test.git;a=blob;f=csit/testplans/of-config-basic.txt
-
-3. Have you integrated odlparent 3 / yangtools 2? (Yes/No/NA)
-
- - No
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone?
- (Yes/No)
-
- - No
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-===============
-OpenFlow Plugin
-===============
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-None
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes
-
- - If you had Tentative APIs, have they been moved to Provisional or dropped? No
-
- - If any of your Tentative APIs were dropped, have you notified all projects
- that were expecting them? No API dropped.
- - Also please list all dropped APIs. - None
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? Yes
-
-3. Were there any project-specific deliverables planned for this milestone? Yes (Mainly Bug Fixes)
-
- - If so, were they delivered? Yes
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? Yes
-
- - `Existing Features <https://git.opendaylight.org/gerrit/gitweb?p=openflowplugin.git;a=tree;f=features-aggregator;h=cdbabd213e7dbcc1944e3e9d389f99c22c17a670;hb=HEAD>`_
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- * **odl-openflowjava-protocol**: OpenFlow protocol library implementation
- * **odl-openflowplugin-nsf-model**: OpenFlowPlugin exposed YANG models for device configuration and operational state.
- * **odl-openflowplugin-southbound**: OpenFlow Southbound plugin implementation
- * **odl-openflowplugin-app-config-pusher**: Pushes node configuration changes to OpenFlow device
- * **odl-openflowplugin-app-forwardingrules-manager**: Sends device configuration from config datastore to OpenFlow device incrementally.
- * **odl-openflowplugin-app-forwardingrules-sync**: Sends device configuration from config datastore to OpenFlow devices. It uses batching and push the diffs between previous and new configuration. forwardingrules-sync can be replaced with forwardingrules-manager and vice versa.
- * **odl-openflowplugin-app-table-miss-enforcer**: Configures table miss flows to OpenFlow device
- * **odl-openflowplugin-app-topology**: Discovers topology of connected OpenFlow devices
- * **odl-openflowplugin-nxm-extensions**: Support for OpenFlow Nicira Extensions
- * **odl-openflowplugin-onf-extensions**: Support for Open Networking Foundation Extensions
- * **odl-openflowplugin-flow-services**: Wrapper feature for standard applications
- * **odl-openflowplugin-flow-services-rest**: odl-openflowplugin-flow-services feature with REST interface
- * **odl-openflowplugin-flow-services-ui**: odl-openflowplugin-flow-services feature with REST interface and UI
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- * **User Guide(s):**
-
- * :doc:`../../../user-guide/openflow-plugin-project-user-guide`
-
- * **Developer Guide(s):**
-
- * :doc:`../../../developer-guide/openflow-plugin-project-developer-guide`
-
- * Release notes
-
-2. Have you checked in a reStructuredText outline to the docs repository? Yes
-
- - `Docs module <https://git.opendaylight.org/gerrit/gitweb?p=openflowplugin.git;a=tree;f=docs;h=cb5e9a625ed57e1292eff8556bbe8cf99eb2c745;hb=HEAD>`_
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features? Yes
-
- - ` CSIT Tests <https://jenkins.opendaylight.org/releng/view/openflowplugin/>`_
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? No
-
- - Not done yet, will be available by M3
-
-3. Have you integrated odlparent 3 / yangtools 2? No
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone? Yes (Mostly bug fixing)
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-======
-OpFlex
-======
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes
-
- - If you had Tentative APIs, have they been moved to Provisional or dropped?
- N/A
- - If any of your Tentative APIs were dropped, have you notified all projects
- that were expecting them? N/A
- - Also please list all dropped APIs: N/A
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? Yes
-
-3. Were there any project-specific deliverables planned for this milestone?
- No
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? Yes (N/A)
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - N/A
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - User guide for agent-ovs daemon
- - Developer guide for libopflex, genie, agent-ovs
- - Install guide for Red Hat/CentOS
- - Release notes (mandatory)
-
-2. Have you checked in a reStructuredText outline to the docs repository? Yes
-
- - `User guide <https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/opflex-agent-ovs-user-guide.rst;h=d7212fc4e9f0c1d2d188ee513868cc4c92fed14e;hb=refs/heads/master>`_
- - `libopflex developer guide <https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/opflex-libopflex-developer-guide.rst;h=2f8d371e6c67d3339dd6c0d5b199e5ef9232c613;hb=refs/heads/master>`_
- - `agent-ovs developer guide <https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/opflex-agent-ovs-developer-guide.rst;h=b7840c50ffc9ec7ab7dc38809707f0574e23a018;hb=refs/heads/master>`_
- - `genie developer guide <https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/opflex-genie-developer-guide.rst;h=72128c3db852ca092865547cec22b507f55524b0;hb=refs/heads/master>`_
- - `Install guide <https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/getting-started-guide/project-specific-guides/opflex.rst;h=9c732221727455ad35072c225098b8eb91b610e1;hb=refs/heads/master>`_
- - Release notes pending
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features?
- Yes
-
- - No top-level features
- - Testing exists in separate infrastructure
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? (Yes/No)
-
- - `System Test <https://wiki.opendaylight.org/view/OpFlex:Oxygen_Feature_Integration_System_Test>`_
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone?
- No
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy? Yes
+++ /dev/null
-=====
-OVSDB
-=====
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-None
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes
-
- - If you had Tentative APIs, have they been moved to Provisional or dropped? No
-
- - If any of your Tentative APIs were dropped, have you notified all projects
- that were expecting them? No API dropped.
- - Also please list all dropped APIs. - None
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? Yes
-
-3. Were there any project-specific deliverables planned for this milestone? Yes (Mainly Bug Fixes)
-
- - If so, were they delivered? Yes
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? Yes
-
- - `Existing Features <https://git.opendaylight.org/gerrit/gitweb?p=ovsdb.git;a=tree;f=southbound/southbound-features;h=99e3dbd349e18886312a82db325f54ae2fb70ac6;hb=HEAD>`_
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - **OVSDB Southbound Plugin**:
-
- * **odl-ovsdb-southbound-api**: User should install this feature if they want to load the yang models expose by the plugin and want to write their own plugin implementation.
- * **odl-ovsdb-southbound-impl** : User should install this feature if they want to consume plugin using the java bindings.
- * **odl-ovsdb-southbound-impl-rest**: User should install this feature if they want to write application that consume plugin using java binding as well as rest interface.
- * **odl-ovsdb-southbound-impl-ui**: User should install this feature if they want to use bindings provided by odl-ovsdb-southbound-impl-rest and also want to load the Dlux GUI.
-
- - **OVSDB Hardware vTEP Plugin**:
-
- * **odl-ovsdb-hwvtepsouthbound-api**: User should install this feature if they want to load the yang models expose by the plugin and want to write their own plugin implementation.
- * **odl-ovsdb-hwvtepsouthbound** : User should install this feature if they want to consume plugin using the java bindings.
- * **odl-ovsdb-hwvtepsouthbound-rest**: User should install this feature if they want to write application that consume plugin using java binding as well as rest interface.
- * **odl-ovsdb-hwvtepsouthbound-ui**: User should install this feature if they want to use bindings provided by odl-ovsdb-hwvtepsouthbound-rest and also want to load the dlux GUI.
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- * **User Guide(s):**
-
- * :doc:`OVSDB User Guide <../../../user-guide/ovsdb-user-guide>`
-
- * **Developer Guide(s):**
-
- * :doc:`OVSDB Developer Guide <../../../developer-guide/ovsdb-developer-guide>`
-
- * Release notes
-
-2. Have you checked in a reStructuredText outline to the docs repository? Yes
-
- - `Docs module <https://git.opendaylight.org/gerrit/gitweb?p=ovsdb.git;a=tree;f=docs;h=5369a85700cc02e8a9945fa7b1b0926c0f6e295f;hb=HEAD>`_
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features? Yes
-
- - ` CSIT Tests <https://jenkins.opendaylight.org/releng/view/ovsdb/>`_
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? No
-
- - Not done yet, will be available by M3
-
-3. Have you integrated odlparent 3 / yangtools 2? No
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone? Yes (Mostly bug fixing)
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-=========
-P4 Plugin
-=========
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes/No
-
- - Yes, https://wiki.opendaylight.org/view/P4_Plugin:Oxygen:Release_Plan#Externally_Consumable_APIs
- - No dropped APIs.
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? (Yes/No)
-
- - Yes.
-
-3. Were there any project-specific deliverables planned for this milestone?
- Yes/No
-
- - No.
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? (Yes/No)
-
- - Yes, https://git.opendaylight.org/gerrit/gitweb?p=integration/distribution.git;a=blob;f=features/repos/index/pom.xml
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/release-notes/projects/p4plugin.rst
- - odl-p4plugin-all
- - odl-p4plugin-netconf-adapter
- - odl-p4plugin-runtime
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - developer guide
- - user guide
- - Release notes (mandatory).
-
-2. Have you checked in a reStructuredText outline to the docs repository? (Yes/No)
-
- - Yes.
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/p4plugin-user-guide.rst
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/p4plugin-developer-guide.rst
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features?
- (Yes/No)
-
- - No, we are busy with it now.
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? (Yes/No)
-
- - Yes, https://git.opendaylight.org/gerrit/gitweb?p=integration/test.git;a=blob;f=csit/testplans/p4plugin-basic.txt
-
-3. Have you integrated odlparent 3 / yangtools 2? (Yes/No/NA)
-
- - No.
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone?
- (Yes/No)
-
- - No.
-
-2. Have you updated your project facts with the project type category? Yes.
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes.
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-===========
-Packetcable
-===========
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes
-
- - If you had Tentative APIs, have they been moved to Provisional or dropped?
- There were no Tentative APIs in the Packetcable project.
-
-2. Are all your inter-project dependencies resolved? Yes
-
-3. Were there any project-specific deliverables planned for this milestone?
- No
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository?
- Yes, but there are no new features for the Oxygen release of Packetcable
- so no Gerrit patch is applicable.
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - odl-packetcable-policy-server
- - The Packetcable Policy Server enables flow-based dynamic QoS for DOCSIS
- infrastructure-based systems utilizing the COPS protocols.
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - Packetcable user/operator guide (includes install guide)
- - Packetcable developer guide
- - Packetcable Oxygen Release notes
-
-2. Have you checked in a reStructuredText outline to the docs repository? No
-
- - As there are no planned changes to the project documentation for the
- Oxygen release, the current document versions in the master branch
- will be used.
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features?
- Yes
-
- - https://jenkins.opendaylight.org/releng/view/packetcable/job/packetcable-csit-1node-pcmm-all-oxygen/61/robot/
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature?
- No - Packetcable has no (official) stable features at this time.
-
-3. Have you integrated odlparent 3 / yangtools 2? No
-
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone?
- No
-
-2. Have you updated your project facts with the project type category?
- Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy?
- Yes
+++ /dev/null
-=========================
-Service Function Chaining
-=========================
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes
-
- - If you had Tentative APIs, have they been moved to Provisional or dropped?
- N/A
-
- - If any of your Tentative APIs were dropped, have you notified all projects
- that were expecting them? N/A
-
- - Also please list all dropped APIs.
- No APIs were dropped, but we did deprecate the RSP creation via RPC,
- and it will be removed in Fluorine.
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? Yes
-
-3. Were there any project-specific deliverables planned for this milestone? No
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? No
-
- There will be 2 new SFC features in Oxygen: odl-sfc-shell and odl-sfc-statistics.
- The odl-sfc-shell feature has been added to the integration git repo
- in the gerrit patch below, but the odl-sfc-statistics feature is not
- ready yet and will be added soon.
-
- - https://git.opendaylight.org/gerrit/65684
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - For top-level and user-facing features, please provide a one-sentence
- description a developer and/or user would find helpful.
-
- - Top level, user-facing SFC features
-
- - odl-sfc-netconf: Provides functionality to communicate with Netconf capable Service Functions.
- - odl-sfc-scf-openflow: SFC stand-alone openflow classifier.
- - odl-sfc-scf-vpp: SFC stand-alone vpp classifier.
- - odl-sfc-openflow-renderer: Renderer functionality for OpenFlow capable switches.
- - odl-sfclisp: Programs LISP capable switches.
- - odl-sfc-sb-rest: Implements a South Bound Rest interface to send configuration to REST-capable switches.
- - odl-sfc-ui: This feature is the SFC User Interface.
- - odl-sfc-vnfm-tacker: Tacker VNF Manager interface.
- - odl-sfc-ios-xe-renderer: Renderer functionality for IO XE switches that use netconf.
- - odl-sfc-vpp-renderer: Renderer functionality for fd.io VPP (Vector Packet Processor) switches that use netconf.
- - odl-sfc-pot: This feature implements a Proof of Transit for the Service Functions.
-
- - Top level, non-user-facing SFC features consumed by the user-facing features above
-
- - odl-sfc-genius: This feature implements the Genius utilities created by SFC project.
- - odl-sfc-model: This feature defines and implements the SFC data model as specified here https://datatracker.ietf.org/doc/rfc7665/
- - odl-sfc-pot-netconf-renderer: This feature implements the Netconf rendering for the Proof of Transit for the Service Functions.
- - odl-sfc-provider: This feature provides an easy-to-use interface to the sfc-model.
- - odl-sfc-provider-rest: This feature provides no functionality, and just installs the necessary features for SFC restconf.
- - odl-sfc-ovs: This feature provides functionality for SFC to communicate with OVSDB for SFF configuration.
- - odl-sfc-test-consumer: This feature is used for testing only.
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - A user guide for the SFC project.
- - A developer guide for the SFC project.
- - Release notes (mandatory) [2]_.
-
-2. Have you checked in a reStructuredText outline to the docs repository? No
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features? Yes
-
- - https://jenkins.opendaylight.org/releng/view/sfc/
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? No
-
- - We're not ready with this yet.
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone? No
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-====
-SNMP
-====
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-None
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes
-
- - If you had Tentative APIs, have they been moved to Provisional or dropped?
- Yes
- - If any of your Tentative APIs were dropped, have you notified all projects
- that were expecting them? N/A
- - Also please list all dropped APIs. N/A
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? Yes
-
-3. Were there any project-specific deliverables planned for this milestone?
- No
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? Yes
-
- - `Features <https://git.opendaylight.org/gerrit/gitweb?p=snmp.git;a=blob_plain;f=features/features-snmp/pom.xml;hb=HEAD>`_
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- :odl-snmp-plugin: Provides basic Southbound SNMP protocol support
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - One user/operator guide section per user-facing feature.
- - One developer guide per top-level feature.
- - An installation guide for any top-level features that require more than
- feature:install <feature-name> to install.
- - Release notes (mandatory) [2]_.
- - Optional tutorials and how-tos.
-
-2. Have you checked in a reStructuredText outline to the docs repository? No
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features?
- No
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? No
-
-3. Have you integrated odlparent 3 / yangtools 2? No
-
- - Not yet, since upstream dependencies haven't fully integrated yet.
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone?
- No
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-========
-SNMP4SDN
-========
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes
-
- - If you had Tentative APIs, have they been moved to Provisional or dropped?
- No tentative APIs.
- - If any of your Tentative APIs were dropped, have you notified all projects
- that were expecting them? N/A
- - Also please list all dropped APIs. N/A
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? No new dependencies.
-
-3. Were there any project-specific deliverables planned for this milestone?
- No
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? Yes
-
- - https://git.opendaylight.org/gerrit/gitweb?p=integration/distribution.git;a=blob;f=features/repos/index/pom.xml
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - odl-snmp4sdn-snmp4sdn: install the SNMP4SDN Plugin as well as all the dependencies it needs
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - One user/operator guide section per user-facing feature.
- - One developer guide per top-level feature.
- - An installation guide for any top-level features that require more than
- feature:install <feature-name> to install.
- - Release notes (mandatory) [2]_.
- - Optional tutorials and how-tos.
-
-2. Have you checked in a reStructuredText outline to the docs repository? Yes
-
- - https://git.opendaylight.org/gerrit/#/c/44760/
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features?
-
- - No, system test waiver.
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? Yes
-
- - https://wiki.opendaylight.org/view/SNMP4SDN:Test_Plan
-
-3. Have you integrated odlparent 3 / yangtools 2? No
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone?
- No
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-============
-SXP
-============
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes
-
- - If you had Tentative APIs, have they been moved to Provisional or dropped?
- N/A
- - If any of your Tentative APIs were dropped, have you notified all projects
- that were expecting them? N/A
- - Also please list all dropped APIs. N/A
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? Yes
-
-3. Were there any project-specific deliverables planned for this milestone?
- No
-
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? Yes/No)
-
- - https://git.opendaylight.org/gerrit/#/c/59781/
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - odl-sxp-controller - Implementation of the SXP protocol
- - odl-sxp-route - Masks the ODL cluster as a single device for the external
- SXP devices
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - Developer guide
- - User guide
- - Release notes (mandatory)
-
-2. Have you checked in a reStructuredText outline to the docs repository? Yes
-
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/sxp-user-guide.rst;h=ea2ce60ed85c9be80e9049260492e33814c34ab5;hb=HEAD
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/sxp-developer-guide.rst;h=020eae563872c7c292eeebe5893068ae85935f05;hb=HEAD
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features?
- Yes
-
- - https://jenkins.opendaylight.org/releng/view/sxp/job/sxp-csit-1node-basic-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/sxp/job/sxp-csit-1node-filtering-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/sxp/job/sxp-csit-1node-periodic-performance-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/sxp/job/sxp-csit-1node-topology-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/sxp/job/sxp-csit-3node-periodic-clustering-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/sxp/job/sxp-csit-3node-periodic-routing-all-oxygen/
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? Yes
-
- - https://wiki.opendaylight.org/view/SXP:Oxygen:System_Test_Plan
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone?
- No
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
-
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-====
-TSDR
-====
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes
-
- - If you had Tentative APIs, have they been moved to Provisional or dropped?
- N/A
- - If any of your Tentative APIs were dropped, have you notified all projects
- that were expecting them? N/A
- - Also please list all dropped APIs.
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? Yes
-
-3. Were there any project-specific deliverables planned for this milestone?
- No
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? Yes
-
- - https://git.opendaylight.org/gerrit/#/c/65830/
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/release-notes/projects/tsdr.rst
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - User Guide(s).
- - Installation Guide(s).
- - Release notes (mandatory).
- - Tutorials and how-tos.
-
-2. Have you checked in a reStructuredText outline to the docs repository? Yes
-
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/tsdr-user-guide.rst
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features?
- Yes
-
- - https://jenkins.opendaylight.org/releng/view/tsdr/
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? Yes
-
- - https://wiki.opendaylight.org/view/TSDR:TSDR_Oxygen_Testing_with_Results#Test_Cases_.26_Results
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone?
- No
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-======
-Unimgr
-======
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined:
-
- Yes
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)?
-
- Yes
-
-3. Were there any project-specific deliverables planned for this milestone?
-
- No
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository?
-
- Yes
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/release-notes/projects/unimgr.rst
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - User guide
- - Developer guide
-
-2. Have you checked in a reStructuredText outline to the docs repository? No
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features?
- (Yes/No)
-
- - https://jenkins.opendaylight.org/releng/view/unimgr/
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? No
-
-3. Have you integrated odlparent 3 / yangtools 2?
-
- No
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone?
-
- No
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
-
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-===
-USC
-===
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? Yes
-
-3. Were there any project-specific deliverables planned for this milestone?
- No deliverables
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? Yes
-
- - https://git.opendaylight.org/gerrit/gitweb?p=integration/distribution.git;a=blob;f=features/repos/index/pom.xml;
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/release-notes/projects/usc.rst;
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - User Guide, Developer Guide, Tutorials
-
-2. Have you checked in a reStructuredText outline to the docs repository? Yes
-
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/unified-secure-channel.rst;
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/unified-secure-channel.rst;
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features? Yes
-
- - https://jenkins.opendaylight.org/releng/view/usc/
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? Yes
-
- - https://wiki.opendaylight.org/view/USC:Integration_Test
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone? No deliverables
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-===
-VTN
-===
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes
-
- - If you had Tentative APIs, have they been moved to Provisional or dropped?
- N/A
- - If any of your Tentative APIs were dropped, have you notified all projects
- that were expecting them? N/A
- - Also please list all dropped APIs.
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? Yes
-
-3. Were there any project-specific deliverables planned for this milestone?
- - No
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? Yes
-
- - https://git.opendaylight.org/gerrit/gitweb?p=integration/distribution.git;a=blob;f=features/repos/index/pom.xml;h=d9dbcafaed73ad39695a25a06e4e8f0ceb79b904;hb=HEAD
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/release-notes/projects/vtn.rst;h=2533053aa7b2bd5fe0d425f25cf29a67f2671006;hb=HEAD
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/virtual-tenant-network-(vtn).rst;h=810ca51907fb062516244b50a7f7a84ca6a8c9a9;hb=HEAD
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - User Guide(s).
- - Developer Guide(s).
- - Installation Guide(s).
- - Release notes (mandatory).
- - Tutorials and how-tos.
-
-2. Have you checked in a reStructuredText outline to the docs repository? Yes
-
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/virtual-tenant-network-(vtn).rst;h=602e71bdfabc85641794e14a8c72082ed684e33d;hb=HEAD
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features?
- Yes
-
- - https://jenkins.opendaylight.org/releng/view/vtn/
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? Yes
-
- - https://wiki.opendaylight.org/view/OpenDaylight_Virtual_Tenant_Network_(VTN):Integration_Test
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone?
- No
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-==========
-YANG Tools
-==========
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes
-
- - If you had Tentative APIs, have they been moved to Provisional or dropped? Yes
-
- - If any of your Tentative APIs were dropped, have you notified all projects
- that were expecting them? Yes, provided migration patches to downstreams.
- - Also please list all dropped APIs:
- - websocket-server
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? Yes
-
-3. Were there any project-specific deliverables planned for this milestone?
- Yes
-
- - If so, were they delivered? Yes
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? Yes
-
- - Existing feature
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- * **odl-triemap**: Ctrie-based java.util.Map implementation
- * **odl-yangtools-codec**: YANG data XML and JSON codecs
- * **odl-yangtools-common**: Common YANG constants and concepts
- * **odl-yangtools-data-api**: YANG data instance and transformation APIs
- * **odl-yangtools-data**: YANG data instance reference implementation
- * **odl-yangtools-export**: YANG metamodel encoding utilities
- * **odl-yangtools-parser-api**: YANG metamodel and parser APIs
- * **odl-yangtools-parser**: YANG/YIN RFC6020/RFC7950 parser and compiler
- * **odl-yangtools-util**: Core concepts and utilities
- * **odl-yangtools-xpath**: YANG data instance XPath support
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- * **Developer Guide(s):**
-
- * :doc:`../../../developer-guide/yang-tools`
-
- * **Release notes**
-
- * :doc:`../../../release-notes/projects/yangtools`
-
-2. Have you checked in a reStructuredText outline to the docs repository? Yes
-
- - https://git.opendaylight.org/gerrit/66832
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features?
- Yes
-
- - ` CSIT Tests <https://jenkins.opendaylight.org/releng/view/yangtools/job/yangtools-csit-1node-periodic-system-only-oxygen/>`_
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? (Yes/No)
-
- - No, test plan is expected at M4.
-
-3. Have you integrated odlparent 3 / yangtools 2? (Yes/No/NA)
-
- - Yes, https://git.opendaylight.org/gerrit/65892.
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone?
- Yes.
-
- - If so, were they delivered? Yes.
-
-2. Have you updated your project facts with the project type category? Yes
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-============
-Project Name
-============
-
-Please provide updates on any previously-incomplete items from prior milestone
-readouts.
-
-Functionality Freeze:
----------------------
-
-1. Final list of externally consumable APIs defined: Yes/No
-
- - If you had Tentative APIs, have they been moved to Provisional or dropped?
- (Yes/No) <link to release plan>
- - If any of your Tentative APIs were dropped, have you notified all projects
- that were expecting them? (Yes/No) <link to e-mail>
- - Also please list all dropped APIs.
-
-2. Are all your inter-project dependencies resolved (i.e., have the other
- projects you were counting on given you what you needed)? (Yes/No)
-
- - (If no, please list the features you were expecting that have not been delivered)
- - (The respective project [1]_ you were expecting to receive them from)
-
-3. Were there any project-specific deliverables planned for this milestone?
- Yes/No
-
- - (If so, were they delivered? Yes/No)
-
-Karaf Features Defined:
------------------------
-
-1. Are all your project's features that are intended for release added to the
- features.xml and checked into integration git repository? (Yes/No)
-
- - Please provide link to gerrit patch
-
-2. List all top-level, user-facing, and stable Karaf features for your project.
-
- - For top-level and user-facing features, please provide a one-sentence
- description a developer and/or user would find helpful.
-
-Documentation:
---------------
-
-1. List the kinds of documentation you will provide including at least:
-
- - One user/operator guide section per user-facing feature.
- - One developer guide per top-level feature.
- - An installation guide for any top-level features that require more than
- feature:install <feature-name> to install.
- - Release notes (mandatory) [2]_.
- - Optional tutorials and how-tos.
-
-2. Have you checked in a reStructuredText outline to the docs repository? (Yes/No)
-
- - Please provide link to gerrit patch
-
-Integration and Test:
----------------------
-
-1. Have you started automated system testing for your top-level features?
- (Yes/No)
-
- - (If yes, link to test report)
- - (If no, why?)
-
-2. Have you filled out basic system test plan template for each top-level
- feature (karaf and not karaf) and a comprehensive system test plan template
- including functionality, cluster, scalability, performance,
- longevity/stability for each stable feature? (Yes/No)
-
- - (If yes, link to test plans)
- - (If no, why?)
-
-3. Have you integrated odlparent 3 / yangtools 2? (Yes/No/NA)
-
- - (If yes, link to gerrit patch)
-
-Project Specific:
------------------
-
-1. Were there any project-specific deliverables planned for this milestone?
- (Yes/No)
-
- - (If so, were they delivered? Yes/No )
-
-2. Have you updated your project facts with the project type category? (Yes/No)
-
-3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? (Yes/No)
-
-.. [1] Note that you can only reasonably hold a project to something if you
- formally asked for it during the release planning process and the project
- team members acknowledged that ask saying they would do it.
-.. [2] Release notes must be updated prior to a major release. It is a good idea
- to keep release notes as a living document when significant changes are
- made.
-.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html
+++ /dev/null
-===
-AAA
-===
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts?
- Yes, the odlparent 3.0.1 and yangtools 2.0.0 upgrade is still incomplete. There are several issues with upstream odlparent which are found in this `email thread <https://lists.opendaylight.org/pipermail/release/2017-December/013053.html>`_. The upgrade is being completed in this `Pending Patch <https://git.opendaylight.org/gerrit/#/c/64196/>`_.
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
-3. Do you have content in your project documentation? Yes
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- Yes
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Have you started automated system testing for your top-level features? Yes
-
- - https://jenkins.opendaylight.org/releng/view/aaa/
-
-7. Does your project use any ports, including for testing? Yes
-
- - (If yes, list of ports used) Yes, 5435 and 8181.
- - (If yes, have you updated the wiki [3]_ with all ports used? Yes
-
-8. Does your project build successfully in Autorelease? Yes
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-====
-ALTO
-====
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? Yes
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
- - https://git.opendaylight.org/gerrit/#/q/file:%255Ealto-core/standard-service-models/.%252B+project:alto
-
-3. Do you have content in your project documentation? Yes
-
- - ALTO User Guide: 1130, https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/alto-user-guide.rst;h=3093d9d546d2db987307a1fe0cb43daa9a5b4214;hb=HEAD
- - ALTO Developer Guide: 706, https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/alto-developer-guide.rst;h=af75aec33d31a2e92efe1084d17a55aa253a8028;hb=HEAD
- - No pending patch
-
-4. Has your project met the requirements to be included in Maven Central?
- No
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Have you started automated system testing for your top-level features? Yes
-
- - https://jenkins.opendaylight.org/releng/view/alto/job/alto-csit-1node-setup-all-oxygen/
-
-7. Does your project use any ports, including for testing? Yes
-
- - 8181
-
-8. Does your project build successfully in Autorelease? Yes
-
- - https://jenkins.opendaylight.org/releng/view/alto/job/alto-validate-autorelease-oxygen/
-
+++ /dev/null
-===========
-BGP LS PCEP
-===========
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts?
-
- - No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now?
-
- - Yes
-
-3. Do you have content in your project documentation?
-
- - Yes
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/bgp-developer-guide.rst;h=0e5df8030a53fc22aeb044982758f362271d91b3;hb=refs/heads/master
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/bgp-monitoring-protocol-developer-guide.rst;h=d83bbc7dce561e9ac6319cadba0a1460003d9641;hb=refs/heads/master
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/pcep-developer-guide.rst;h=d1b48bfbfb2b91b1002e6fff99cb9360490366ea;hb=refs/heads/master
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/bgp-user-guide.rst;h=307de691444779efdeda065d9f5e98791ef1bfc8;hb=refs/heads/master
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/bgp-monitoring-protocol-user-guide.rst;h=5153494111add81a13c3582d56d240ce782e63ec;hb=refs/heads/master
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/pcep-user-guide.rst;h=8cba92ecc27a7696656486b85649c4f740f8f6f9;hb=refs/heads/master
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
-
- - Yes
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully?
-
- - Yes
-
-6. Have you started automated system testing for your top-level features?
-
- - Yes
- - https://jenkins.opendaylight.org/releng/view/bgpcep/job/bgpcep-csit-1node-periodic-bgp-ingest-mixed-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/bgpcep/job/bgpcep-csit-1node-periodic-bgp-ingest-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/bgpcep/job/bgpcep-csit-1node-periodic-throughpcep-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/bgpcep/job/bgpcep-csit-1node-userfeatures-all-oxygen/
-
-7. Does your project use any ports, including for testing?
-
- - 179 - BGP
- - 1790 - BGP/PCEP
- - 12345 - BMP
- - 4189 - PCEP
-
-8. Does your project build successfully in Autorelease?
-
- - Yes
- - https://jenkins.opendaylight.org/releng/view/bgpcep/job/bgpcep-validate-autorelease-oxygen/
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-====
-BIER
-====
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts?
-
- - No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now?
-
- - Yes
-
-3. Do you have content in your project documentation?
-
- - Yes
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/bier-user-guide.rst
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/bier-developer-guide.rst
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
-
- - Yes
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully?
-
- - Yes
-
-6. Have you started automated system testing for your top-level features?
-
- - Yes
- - https://jenkins.opendaylight.org/releng/view/bier/job/bier-csit-1node-basic-all-oxygen/
-
-7. Does your project use any ports, including for testing?
-
- - No
-
-8. Does your project build successfully in Autorelease?
-
- - Yes
- - https://jenkins.opendaylight.org/releng/view/bier/job/bier-validate-autorelease-oxygen/
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-===
-Coe
-===
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
-3. Do you have content in your project documentation? Yes
-
- - https://git.opendaylight.org/gerrit/#/c/66869/2/docs/setting-up-coe-dev-environment.rst
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- No
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Have you started automated system testing for your top-level features? No
-
-7. Does your project use any ports, including for testing? No
-
-8. Does your project build successfully in Autorelease? Yes
-
- - https://jenkins.opendaylight.org/releng/view/coe/job/coe-validate-autorelease-oxygen/
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
\ No newline at end of file
+++ /dev/null
-============
-Controller
-============
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
-3. Do you have content in your project documentation? Yes
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- Yes
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Have you started automated system testing for your top-level features? Yes
-
- - https://jenkins.opendaylight.org/releng/view/controller/
-
-7. Does your project use any ports, including for testing? Yes
-
- - (If yes, list of ports used) 2550
- - (If yes, have you updated the wiki [3]_ with all ports used? Yes
-
-8. Does your project build successfully in Autorelease? Yes
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-.. Instructions
-.. 1. Replace Project Name with your actual project name, ensure you have
-.. the same number of ='s as the length of your project in the line before
-.. and the line after.
-.. 2. Remove the (Yes/No) answer at the end of each question with your actual
-.. response: Yes or No
-.. Note: For Question 5, the response could be: No Deliverables
-.. 3. For detailed information on each question, use a sub list with a -
-.. in front that aligns with the text above and ensure you have a blank
-..
-
-======
-DAEXIM
-======
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts?
-
- - Yes. Bump odlparent version to 3.0.1 and yangtool to 2.0.0. Changeset is
- available, but builds are failing.
- https://git.opendaylight.org/gerrit/#/c/66431/
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now?
-
- - Yes
- - No new API in this release
-
-3. Do you have content in your project documentation?
-
- - Yes
- - :ref:`daexim user guide <daexim-user-guide>`: 892 words
- - :ref:`daexim developer guide <daexim-dev-guide>`: 118 words
- - Both added via: https://git.opendaylight.org/gerrit/#/c/62941/
- - Update to user guide: https://git.opendaylight.org/gerrit/#/c/66279/
-
-4. Has your project met the requirements to be included in Maven Central?
-
- - No. Missing signature, license, developer information, scm, etc.
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully?
-
- - No Deliverables
-
-6. Have you started automated system testing for your top-level features?
-
- - Yes
- - https://jenkins.opendaylight.org/releng/view/daexim/job/daexim-csit-1node-basic-only-oxygen/
-
-7. Does your project use any ports, including for testing?
-
- - No
-
-8. Does your project build successfully in Autorelease?
-
- - Yes
-
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-========================
-Integration/Distribution
-========================
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
-3. Do you have content in your project documentation? Yes
-
- - :doc:`../../../user-guide/distribution-version-user-guide`
- - :doc:`../../../developer-guide/distribution-version`
- - :doc:`../../../developer-guide/distribution-test-features`
- - :doc:`../../../getting-started-guide/common-features/clustering`
- - :doc:`../../../getting-started-guide/common-features/persistence_and_backup`
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- No, missing GPG signing.
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? Yes
-
-6. Have you started automated system testing for your top-level features? Yes
-
- - https://jenkins.opendaylight.org/releng/view/distribution
-
-7. Does your project use any ports, including for testing? No
-
-8. Does your project build successfully in Autorelease? Yes
-
- - https://jenkins.opendaylight.org/releng/view/distribution/job/integration-distribution-validate-autorelease-oxygen
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-====
-DLUX
-====
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
- - No patches
-
-3. Do you have content in your project documentation? Yes
-
- - Developer guide, 1600
- - https://git.opendaylight.org/gerrit/#/c/63280/
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- No
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Have you started automated system testing for your top-level features? Yes
-
- - https://git.opendaylight.org/gerrit/#/c/29612/
- Outdated patch and due lack of developers we are not working on it.
-
-7. Does your project use any ports, including for testing? Yes
-
- - 8181
- - (If yes, have you updated the wiki [3]_ with all ports used?) Yes
-
-8. Does your project build successfully in Autorelease? Yes
-
- - Autorelease looks broken now, but DLUX artifacts are building
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-========
-DLUXApps
-========
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
- - No patches
-
-3. Do you have content in your project documentation? Yes
-
- - Developer guide, 1600
- - https://git.opendaylight.org/gerrit/#/c/63280/
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- No
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Have you started automated system testing for your top-level features? Yes
-
- - https://jenkins.opendaylight.org/releng/view/dluxapps/job/dluxapps-csit-1node-yangman-all-oxygen/
-
-7. Does your project use any ports, including for testing? Yes
-
- - 8181
- - (If yes, have you updated the wiki [3]_ with all ports used?) Yes
-
-8. Does your project build successfully in Autorelease? Yes
-
- - Autorelease looks broken now, but DLUXApps artifacts are building
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-.. Instructions
-.. 1. Replace Project Name with your actual project name, ensure you have
-.. the same number of ='s as the length of your project in the line before
-.. and the line after.
-.. 2. Remove the (Yes/No) answer at the end of each question with your actual
-.. response: Yes or No
-.. Note: For Question 5, the response could be: No Deliverables
-.. 3. For detailed information on each question, use a sub list with a -
-.. in front that aligns with the text above and ensure you have a blank
-..
-
-====
-eman
-====
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
- - (Link to gerrit search for patches modifying the API [1]_)
-
-3. Do you have content in your project documentation? Yes
-
- - Release notes, WC 266, https://git.opendaylight.org/gerrit/#/c/63036/3/docs/getting-started-guide/project-release-notes/eman.rst
- - Developer guide, WC 503, https://git.opendaylight.org/gerrit/#/c/56215/1/docs/developer-guide/eman-developer-guide.rst
- - User guide, WC 483, https://git.opendaylight.org/gerrit/#/c/56215/1/docs/user-guide/eman-user-guide.rst
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- Yes
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Have you started automated system testing for your top-level features? No
-
- - Automated testing not implemented
-
-7. Does your project use any ports, including for testing? No
-
-
-8. Does your project build successfully in Autorelease? Yes
-
- - https://jenkins.opendaylight.org/releng/view/eman/job/eman-distribution-check-oxygen/23/
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-====
-FaaS
-====
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
-3. Do you have content in your project documentation? Yes
-
-4. Has your project met the requirements to be included in Maven Central [2]_? No
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Have you started automated system testing for your top-level features? No
-
-7. Does your project use any ports, including for testing? Yes
-
- - 6641, 6653
- - If yes, have you updated the wiki [3]_ with all ports used? Yes
-
-8. Does your project build successfully in Autorelease? Yes
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-======
-Genius
-======
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
- - No change in externlly accessible Stable APIs. New APIs will be added.
-
-3. Do you have content in your project documentation? Yes
-
- - Genius User Guide, WC: 1617,
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/genius-user-guide.rst;h=1385ebb30901336ff50cf3a1fcc161cd72fd5c8d;hb=HEAD
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- No
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Have you started automated system testing for your top-level features? Yes
-
- - https://jenkins.opendaylight.org/releng/view/genius/
-
-7. Does your project use any ports, including for testing? No
-
-8. Does your project build successfully in Autorelease? Yes
-
- - https://jenkins.opendaylight.org/releng/job/genius-validate-autorelease-oxygen/306/
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-================
-GROUPBASEDPOLICY
-================
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
- - https://git.opendaylight.org/gerrit/#/q/file:%255E.*%255C.yang%252B+status:merged+project:groupbasedpolicy
-
-3. Do you have content in your project documentation? Yes
-
- - User's Guide: http://docs.opendaylight.org/en/stable-nitrogen/user-guide/group-based-policy-user-guide.html
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- No
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Have you started automated system testing for your top-level features? Yes
-
- - https://jenkins.opendaylight.org/releng/view/groupbasedpolicy/job/groupbasedpolicy-csit-1node-3-node-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/groupbasedpolicy/job/groupbasedpolicy-csit-1node-6node-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/groupbasedpolicy/job/groupbasedpolicy-csit-3node-clustering-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/groupbasedpolicy/job/groupbasedpolicy-csit-1node-sxp-only-oxygen/
-
-7. Does your project use any ports, including for testing? No
-
-8. Does your project build successfully in Autorelease? Yes
- - https://jenkins.opendaylight.org/releng/view/groupbasedpolicy/job/groupbasedpolicy-validate-autorelease-oxygen/26/
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-===============
-Honeycomb - VBD
-===============
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
- - https://git.opendaylight.org/gerrit/#/q/file:%255Eapi/src/main/yang/.%252B+status:merged+project:honeycomb/vbd
-
-3. Do you have content in your project documentation? No
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- No
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Have you started automated system testing for your top-level features? No
-
- - all features are marked as experimental, no top level stable features yet.
-
-7. Does your project use any ports, including for testing? No
-
-8. Does your project build successfully in Autorelease? Yes
-
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-==========
-Infrautils
-==========
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
-3. Do you have content in your project documentation? Yes
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- Yes
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Have you started automated system testing for your top-level features? Yes
-
- - https://jenkins.opendaylight.org/releng/view/infrautils/
-
-7. Does your project use any ports, including for testing? Yes
-
- - (If yes, list of ports used) 6886
- - (If yes, have you updated the wiki [3]_ with all ports used? Yes
-
-8. Does your project build successfully in Autorelease? Yes
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-========
-JSON-RPC
-========
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
-3. Do you have content in your project documentation? Yes
-
- - User and Developer guides https://git.opendaylight.org/gerrit/67438 1793
- and 85 respectively.
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- No, working on it.
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? Yes
-
-6. Have you started automated system testing for your top-level features? No
-
- - We can do only minimal testing in this release
- as the corresponding external to ODL components are not yet upstreamed.
-
-7. Does your project use any ports, including for testing? No
-
- - No predetermined standard ports. The JSON-RPC extension can be configured
- to use abitrary port(s)
-
-8. Does your project build successfully in Autorelease? No
- - Builds OK with master.
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-========
-L2Switch
-========
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? *No*
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? *Yes*
-
- - Link to gerrit search for patches modifying the API [1]_
-
-3. Do you have content in your project documentation? *Yes*
-
- - User Guide (1838 words) [5]_
- - Developer Guide (2240 words) [6]_
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- *No*
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? *No Deliverables*
-
-6. Have you started automated system testing for your top-level features? *Yes*
-
- - Test report [7]_
- - There are possible regressions in Oxygen that need to be investigated
-
-7. Does your project use any ports, including for testing? *No*
-
-8. Does your project build successfully in Autorelease? *Yes*
-
- - link to successful autorelease job [4]_
-
-.. [1] https://git.opendaylight.org/gerrit/#/q/status:merged+project:l2switch+file:%22%255E.*/model/.%252B%255C.yang%2524%22
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-validate-autorelease-oxygen/35
-.. [5] https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/l2switch-user-guide.rst;h=381e9f9b3b3e5e6a072af58d011f5f23411f6b95;hb=refs/heads/master
-.. [6] https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/l2switch-developer-guide.rst;h=96d7789d80c3597a10a276e9a17c0796b62634d6;hb=refs/heads/master
-.. [7] https://jenkins.opendaylight.org/releng/view/l2switch/job/l2switch-csit-1node-switch-all-oxygen/
+++ /dev/null
-=================
-LISP Flow Mapping
-=================
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
-3. Do you have content in your project documentation? Yes
-
- - User Guide: http://docs.opendaylight.org/en/stable-nitrogen/user-guide/lisp-flow-mapping-user-guide.html
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- No
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? Yes
-
-6. Have you started automated system testing for your top-level features? Yes
-
- - https://jenkins.opendaylight.org/releng/view/lispflowmapping/
-
-7. Does your project use any ports, including for testing? Yes
-
- - UDP port 4342
- - (If yes, have you updated the wiki [3]_ with all ports used? Yes)
-
-8. Does your project build successfully in Autorelease?
-
- - Autorelease is broken now due to the odlparent/yangtools version bump.
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-====
-NEMO
-====
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
-3. Do you have content in your project documentation? Yes
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- Yes
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Have you started automated system testing for your top-level features? Yes
-
- - https://jenkins.opendaylight.org/releng/view/nemo/
-
-7. Does your project use any ports, including for testing? No
-
-8. Does your project build successfully in Autorelease? Yes
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-
-=======
-Netconf
-=======
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
-3. Do you have content in your project documentation? Yes
-
- - http://docs.opendaylight.org/en/stable-nitrogen/release-notes/projects/netconf.html#documentation
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- Yes
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Have you started automated system testing for your top-level features? Yes
-
- - https://jenkins.opendaylight.org/releng/view/netconf/
-
-7. Does your project use any ports, including for testing? Yes
-
- - http://docs.opendaylight.org/en/stable-nitrogen/release-notes/projects/netconf.html#security-considerations
- - (If yes, have you updated the wiki [3]_ with all ports used? No) Netconf call-home TCP port 6666 is missing
-
-8. Does your project build successfully in Autorelease? Yes
-
- - https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-validate-autorelease-oxygen/226/
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-=======
-NetVirt
-=======
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
-3. Do you have content in your project documentation? Yes
-
- - :doc:`../../submodules/netvirt/docs/user-guide/index`
- - :doc:`../../submodules/netvirt/docs/openstack-guide/index`
- - :doc:`../../submodules/netvirt/docs/developer-guide/index`
- - :doc:`../../submodules/netvirt/docs/contributor-guide/index`
-
-4. Has your project met the requirements to be included in Maven Central [2]_? Yes
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No deliverables
-
-6. Have you started automated system testing for your top-level features? Yes
-
- https://jenkins.opendaylight.org/releng/view/netvirt-csit/
-
-7. Does your project use any ports, including for testing? No
-
-8. Does your project build successfully in Autorelease? Yes
-
- - https://jenkins.opendaylight.org/releng/job/netvirt-validate-autorelease-oxygen/
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-.. Instructions
-.. 1. Replace Project Name with your actual project name, ensure you have
-.. the same number of ='s as the length of your project in the line before
-.. and the line after.
-.. 2. Remove the (Yes/No) answer at the end of each question with your actual
-.. response: Yes or No
-.. Note: For Question 5, the response could be: No Deliverables
-.. 3. For detailed information on each question, use a sub list with a -
-.. in front that aligns with the text above and ensure you have a blank
-..
-
-==================
-Neutron Northbound
-==================
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts?
-
- No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now?
-
- No. The following three patches will be merged. They don't break API
- compatibility. The breaking part are postponed to F.
-
- - https://git.opendaylight.org/gerrit/#/c/66915/
- - https://git.opendaylight.org/gerrit/#/c/60170/
- - https://git.opendaylight.org/gerrit/#/c/51981/
-
-3. Do you have content in your project documentation?
-
- Yes. No update since Nitrgen cycle.
-
- - 434 words https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/neutron-northbound.rst;hb=HEAD
- - 702 words https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/neutron-service-developer-guide.rst;hb=HEAD
- - 808 words https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/neutron-service-user-guide.rst;hb=HEAD
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
-
- Yes
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully?
-
- No Deliverables
-
-6. Have you started automated system testing for your top-level features?
-
- System test waiver is applied.
- - https://lists.opendaylight.org/pipermail/release/2017-October/012703.html
-
- Yes with OpenStack CI.
- - https://review.openstack.org/#/q/project:openstack/networking-odl
-
- Also ODL Neutron Northbound is tested with NetVirt project, OPNFV FastDataStack
-
-7. Does your project use any ports, including for testing?
-
- Yes
-
- - (If yes, list of ports used) 8181, 8087
- - (If yes, have you updated the wiki [3]_ with all ports used? Yes
-
-8. Does your project build successfully in Autorelease?
-
- Yes. https://jenkins.opendaylight.org/releng/job/neutron-validate-autorelease-oxygen/36/
-
- - (If yes, link to successful autorelease job [4]_)
- - (If not, explain why)
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-==========
-ODL Parent
-==========
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
-3. Do you have content in your project documentation? Yes
-
- - Developer's Guide: https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/odl-parent-developer-guide.rst
- - Updates forthcoming for 3.0
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- No
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Have you started automated system testing for your top-level features? No
-
- - ODL Parent has a system test waiver
-
-7. Does your project use any ports, including for testing? No
-
-8. Does your project build successfully in Autorelease? N/A
-
- - ODL Parent isn't part of Autorelease
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-=========
-OF-CONFIG
-=========
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
-3. Do you have content in your project documentation? Yes
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- Yes
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Have you started automated system testing for your top-level features? Yes
-
- - https://jenkins.opendaylight.org/releng/view/of-config/
-
-7. Does your project use any ports, including for testing? No
-
-8. Does your project build successfully in Autorelease? Yes
-
- - https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/of-config-validate-autorelease-oxygen/4/
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-===============
-OpenFlow Plugin
-===============
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
-3. Do you have content in your project documentation? Yes
-
- * **User Guide(s):**
-
- * :doc:`../../../user-guide/openflow-plugin-project-user-guide`
-
- * **Developer Guide(s):**
-
- * :doc:`../../../developer-guide/openflow-plugin-project-developer-guide`
-
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- No, GPG/PGP signing part is not done yet.
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? Yes
-
-6. Have you started automated system testing for your top-level features? Yes
-
- - ` CSIT Tests <https://jenkins.opendaylight.org/releng/view/openflowplugin/>`_
-
-7. Does your project use any ports, including for testing? Yes
-
- - 6633, 6653
- - (If yes, have you updated the wiki [3]_ with all ports used? Yes
-
-8. Does your project build successfully in Autorelease? Yes
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-======
-OpFlex
-======
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
-3. Do you have content in your project documentation? Yes
-
- - 2627 ./docs/developer-guide/opflex-libopflex-developer-guide.rst
- - 176 ./docs/developer-guide/opflex-agent-ovs-developer-guide.rst
- - 115 ./docs/developer-guide/opflex-genie-developer-guide.rst
- - 1730 ./docs/user-guide/opflex-agent-ovs-user-guide.rst
- - 1237 ./docs/getting-started-guide/project-specific-guides/opflex.rst
- - 5885 total
-
-4. Has your project met the requirements to be included in Maven Central?
- N/A
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Have you started automated system testing for your top-level features? N/A
-
-7. Does your project use any ports, including for testing? No
-
-8. Does your project build successfully in Autorelease? N/A
+++ /dev/null
-.. Instructions
-.. 1. Replace Project Name with your actual project name, ensure you have
-.. the same number of ='s as the length of your project in the line before
-.. and the line after.
-.. 2. Remove the (Yes/No) answer at the end of each question with your actual
-.. response: Yes or No
-.. Note: For Question 5, the response could be: No Deliverables
-.. 3. For detailed information on each question, use a sub list with a -
-.. in front that aligns with the text above and ensure you have a blank
-..
-
-=====
-OVSDB
-=====
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
- - (Link to gerrit search for patches modifying the API [1]_)
-
-3. Do you have content in your project documentation? Yes
-
- - :doc:`OVSDB User Guide <../../../user-guide/ovsdb-user-guide>`
-
- - :doc:`OVSDB Developer Guide <../../../developer-guide/ovsdb-developer-guide>`
-
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- No
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables (bug fixes only)
-
-6. Have you started automated system testing for your top-level features? Yes
-
- - ` CSIT Tests <https://jenkins.opendaylight.org/releng/view/ovsdb/>`_
-
-7. Does your project use any ports, including for testing? Yes
-
- - 6640, 6641
- - (If yes, have you updated the wiki [3]_ with all ports used? Yes
-
-8. Does your project build successfully in Autorelease? Yes
-
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-=========
-P4 Plugin
-=========
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts?
-
- - Yes, we are busy with automated system test now.
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now?
-
- - Yes
-
-3. Do you have content in your project documentation?
-
- - Yes
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/p4plugin-user-guide.rst
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/p4plugin-developer-guide.rst
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
-
- - Yes
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully?
-
- - Yes
-
-6. Have you started automated system testing for your top-level features?
-
- - No
-
-7. Does your project use any ports, including for testing?
-
- - Yes, the port 50051
-
-8. Does your project build successfully in Autorelease?
-
- - Yes
- - https://jenkins.opendaylight.org/releng/view/p4plugin/job/p4plugin-validate-autorelease-oxygen/
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-===========
-Packetcable
-===========
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts?
- Yes.
-
- - Migration to Yangtools 2 and ODLParent 3 is not complete; understanding is that there's still work happening in the infra to support this.
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now?
- Yes.
-
- - No change in APIs so there is no associated gerrit patch.
-
-3. Do you have content in your project documentation?
- Yes.
-
- - Developer Guide - 1070 words
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/packetcable-developer-guide.rst;h=e7255fc1ec843122650cbb69e45bd96629bbcb3f;hb=refs/heads/master
-
- - User Guide - 1150 words
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/packetcable-user-guide.rst;h=4454d4aaa69337917dfa3fd0593f8b358b8823e6;hb=refs/heads/master
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- No.
-
- - Packetcable is not designated as a "Stable" project.
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully?
- No Deliverables.
-
-6. Have you started automated system testing for your top-level features?
- Yes.
-
- - https://jenkins.opendaylight.org/releng/view/packetcable/job/packetcable-csit-1node-pcmm-all-oxygen/83/robot/
-
-7. Does your project use any ports, including for testing?
- Yes.
-
- - Packetcable uses port 3918; Wiki is updated.
-
-8. Does your project build successfully in Autorelease?
- No.
-
- - Autorelease builds at M2 were successful. We think root cause for current failures is not in the Packetcable project.
-
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-=========================
-Service Function Chaining
-=========================
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
- - https://git.opendaylight.org/gerrit/66569
- - https://git.opendaylight.org/gerrit/66567
- - https://git.opendaylight.org/gerrit/66526
-
-3. Do you have content in your project documentation? Yes ???
-
- - Developer's Guide: http://docs.opendaylight.org/en/stable-nitrogen/developer-guide/service-function-chaining.html
- - User's Guide: http://docs.opendaylight.org/en/stable-nitrogen/user-guide/service-function-chaining.html
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- No
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Have you started automated system testing for your top-level features? Yes
-
- - https://jenkins.opendaylight.org/releng/view/sfc/
-
-7. Does your project use any ports, including for testing? No
-
-8. Does your project build successfully in Autorelease? Yes
-
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-====
-Snmp
-====
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
-3. Do you have content in your project documentation? Yes
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- Yes
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Have you started automated system testing for your top-level features? No
-
- - (If no, explain why) No tests have been developed
-
-7. Does your project use any ports, including for testing? Yes
-
- - (If yes, list of ports used) 161
- - (If yes, have you updated the wiki [3]_ with all ports used? No
-
-8. Does your project build successfully in Autorelease? Yes
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
-
+++ /dev/null
-========
-SNMP4SDN
-========
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
- - Provide a link to a gerrit search for patches modifying the files defined as specifying the API [1]_
- - https://git.opendaylight.org/gerrit/#/q/file:%255Emdsal/model/.%252B+status:merged+project:snmp4sdn
-
-3. Do you have content in your project documentation? Yes
-
-4. Has your project met the requirements to be included in Maven Central [2]_? Yes, except for GPG/PGP
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Have you started automated system testing for your top-level features? No
-
- - Sytem test waiver
-
-7. Does your project use any ports, including for testing? Yes
-
- - Ports used: 162
- - Have you updated the wiki [3]_ with all ports used? Yes
-
-8. Does your project build successfully in Autorelease? No
-
- - Autorelease job [4]_, autorelease-release-oxygen, succeeds in #69, and afterwards all fails
- - SNMP4SDN has been skipped due to project(s) prior in the build sequence failing to build
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-===
-SXP
-===
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
-3. Do you have content in your project documentation? Yes
-
- - SXP developer guide, WC: 521, https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/sxp-developer-guide.rst;h=020eae563872c7c292eeebe5893068ae85935f05;hb=HEAD
- - SXP user guide, WC: 2322, https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/sxp-user-guide.rst;h=ea2ce60ed85c9be80e9049260492e33814c34ab5;hb=HEAD
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- No
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Have you started automated system testing for your top-level features? Yes
-
- - https://jenkins.opendaylight.org/releng/view/sxp/
-
-7. Does your project use any ports, including for testing? Yes
-
- - 64999, 8270
- - (If yes, have you updated the wiki [3]_ with all ports used? Yes)
-
-8. Does your project build successfully in Autorelease? Yes
-
- - https://jenkins.opendaylight.org/releng/view/sxp/job/sxp-validate-autorelease-oxygen/31/
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-====
-TSDR
-====
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts?
- Yes, the odlparent 3.0.2 is incomplete. We've had one patch set pushed out but have to wait for upstream migration complete. https://git.opendaylight.org/gerrit/#/c/66528/
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
-3. Do you have content in your project documentation? Yes
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- Yes except GPG/PGP
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Have you started automated system testing for your top-level features? Yes
-
- - https://jenkins.opendaylight.org/releng/view/tsdr/
-
-7. Does your project use any ports, including for testing? Yes
-
- - (If yes, list of ports used) Yes, 514, 1514, 2055,6343.
- - (If yes, have you updated the wiki [3]_ with all ports used? Yes
-
-8. Does your project build successfully in Autorelease? Yes
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-
-======
-Unimgr
-======
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? (Yes/No)
-
- - No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? (Yes/No)
-
- - Yes
-
-3. Do you have content in your project documentation? (Yes/No)
-
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/uni-manager-plug-in-project.rst;h=7255cfbb94ef317a04395825e45c43068a06522b;hb=HEAD
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/uni-manager-plug-in-developer-guide.rst;h=9c003a8c813c7b1d33dc61aa0b41299560f34d39;hb=HEAD
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- (Yes/No)
-
- - Yes
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? (No Deliverables/Yes/No)
-
- - Yes
-
-6. Have you started automated system testing for your top-level features? (Yes/No)
-
- - https://jenkins.opendaylight.org/releng/view/unimgr/job/unimgr-csit-1node-basic-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/unimgr/job/unimgr-csit-1node-legato-all-oxygen/
-
-7. Does your project use any ports, including for testing? (Yes/No)
-
- - 830 - Netconf
- - 6640, 6641 - OVSDB
-
-8. Does your project build successfully in Autorelease? (Yes/No)
-
- - Yes
- - https://jenkins.opendaylight.org/releng/job/unimgr-validate-autorelease-oxygen/36/
-
-.. [2] http://central.sonatype.org/pages/requirements.html
+++ /dev/null
-===
-USC
-===
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
-3. Do you have content in your project documentation? Yes
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- Yes
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Have you started automated system testing for your top-level features? Yes
-
- - https://jenkins.opendaylight.org/releng/view/usc/
-
-7. Does your project use any ports, including for testing? Yes
-
- - 1068, 1069, 2000, 2007
- - If yes, have you updated the wiki [3]_ with all ports used? Yes
-
-8. Does your project build successfully in Autorelease? Yes
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-===
-VTN
-===
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
-3. Do you have content in your project documentation? Yes
-
- - User's Guide, WC: 24131: https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/virtual-tenant-network-(vtn).rst;h=602e71bdfabc85641794e14a8c72082ed684e33d;hb=HEAD
- - Developer's Guide, WC: 1213: https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/virtual-tenant-network-(vtn).rst;h=810ca51907fb062516244b50a7f7a84ca6a8c9a9;hb=HEAD
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- Yes
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Have you started automated system testing for your top-level features? Yes
-
- - https://jenkins.opendaylight.org/releng/view/vtn/
-
-7. Does your project use any ports, including for testing? Yes
-
- - 8083
- - If yes, have you updated the wiki [3]_ with all ports used? Yes
-
-8. Does your project build successfully in Autorelease? Yes
-
- - https://jenkins.opendaylight.org/releng/view/Validate-Jobs/job/vtn-validate-autorelease-oxygen/
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
-
+++ /dev/null
-==========
-YANG Tools
-==========
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? Yes
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? Yes
-
-3. Do you have content in your project documentation? Yes
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- Yes
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? Yes.
-
-6. Have you started automated system testing for your top-level features? No
-
- - Test plan is being drawn up for M4, features are system-tested by mdsal
- and controller projects.
-
-7. Does your project use any ports, including for testing? No.
-
-8. Does your project build successfully in Autorelease? No
-
- - yangtools follows normal project release and has already released its Oxygen
- artifacts.
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-.. Instructions
-.. 1. Replace Project Name with your actual project name, ensure you have
-.. the same number of ='s as the length of your project in the line before
-.. and the line after.
-.. 2. Remove the (Yes/No) answer at the end of each question with your actual
-.. response: Yes or No
-.. Note: For Question 5, the response could be: No Deliverables
-.. 3. For detailed information on each question, use a sub list with a -
-.. in front that aligns with the text above and ensure you have a blank
-..
-
-============
-Project Name
-============
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? (Yes/No)
-
-2. Has your project achieved API freeze such that all externally accessible
- Stable or Provisional APIs will not be modified after now? (Yes/No)
-
- - (Link to gerrit search for patches modifying the API [1]_)
-
-3. Do you have content in your project documentation? (Yes/No)
-
- - (For each document, provide current word count)
- - (For each document, link to the file in gerrit)
- - (Link to pending gerrit patches waiting approval)
-
-4. Has your project met the requirements to be included in Maven Central [2]_?
- (Yes/No)
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? (No Deliverables/Yes/No)
-
-6. Have you started automated system testing for your top-level features? (Yes/No)
-
- - (If yes, link to test report)
- - (If no, explain why)
-
-7. Does your project use any ports, including for testing? (Yes/No)
-
- - (If yes, list of ports used)
- - (If yes, have you updated the wiki [3]_ with all ports used? Yes/No)
-
-8. Does your project build successfully in Autorelease? (Yes/No)
-
- - (If yes, link to successful autorelease job [4]_)
- - (If not, explain why)
-
-.. [1] Provide a link to a gerrit search for patches modifying the files
- defined as specifying the API. For example:
- https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
-.. [2] http://central.sonatype.org/pages/requirements.html
-.. [3] https://wiki.opendaylight.org/view/Ports
-.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements
+++ /dev/null
-===
-AAA
-===
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project met code freeze [1]_? Yes
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation? Yes
-
-4. Is your documentation complete [2]_? Yes
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Are you running at least one basic automated system test job for each
- top-level feature? Yes
-
- - https://jenkins.opendaylight.org/releng/view/aaa/
-
-7. Do you have any CLM violations? No
-
-**Stable Features (Only for Projects with Stable Features)**
-
-A. Do your stable features fulfill quality requirements [3]_? Yes
-
- -https://sonar.opendaylight.org/component_measures?id=org.opendaylight.aaa%3Aaaa.project
-
-B. Are you running several automated system test jobs [4]_ for each stable
- feature? Yes
-
- - https://jenkins.opendaylight.org/releng/view/aaa/
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance,
- longevity/stability
+++ /dev/null
-====
-ALTO
-====
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts?
-
- - No
-
-2. Has your project met code freeze [1]_?
-
- - No (a few pending patches not merged)
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation?
-
- - Yes
-
-4. Is your documentation complete [2]_?
-
- - Yes
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/alto-developer-guide.rst;h=af75aec33d31a2e92efe1084d17a55aa253a8028;hb=refs/heads/master
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/alto-user-guide.rst;h=3093d9d546d2db987307a1fe0cb43daa9a5b4214;hb=refs/heads/master
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully?
-
- - Yes
-
-6. Are you running at least one basic automated system test job for each
- top-level feature?
-
- - Yes
- - https://jenkins.opendaylight.org/releng/view/alto/job/alto-csit-1node-setup-all-oxygen/
-
-7. Do you have any CLM violations? (Yes/No)
-
- - Yes (security violation because of some dependent libraries)
-
-**Stable Features (Only for Projects with Stable Features)**
-
-A. Do your stable features fulfill quality requirements [3]_?
- N/A (no stable features)
-
-B. Are you running several automated system test jobs [4]_ for each stable
- feature? (Yes/No)
- N/A (no stable features)
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance, longevity/stability
+++ /dev/null
-===========
-BGP LS PCEP
-===========
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts?
-
- - No
-
-2. Has your project met code freeze [1]_?
-
- - Yes
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation?
-
- - Yes
-
-4. Is your documentation complete [2]_?
-
- - Yes
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/bgp-developer-guide.rst;h=0e5df8030a53fc22aeb044982758f362271d91b3;hb=refs/heads/master
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/bgp-monitoring-protocol-developer-guide.rst;h=d83bbc7dce561e9ac6319cadba0a1460003d9641;hb=refs/heads/master
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/pcep-developer-guide.rst;h=d1b48bfbfb2b91b1002e6fff99cb9360490366ea;hb=refs/heads/master
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/bgp-user-guide.rst;h=307de691444779efdeda065d9f5e98791ef1bfc8;hb=refs/heads/master
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/bgp-monitoring-protocol-user-guide.rst;h=5153494111add81a13c3582d56d240ce782e63ec;hb=refs/heads/master
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/pcep-user-guide.rst;h=8cba92ecc27a7696656486b85649c4f740f8f6f9;hb=refs/heads/master
-
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully?
-
- - Yes
-
-6. Are you running at least one basic automated system test job for each
- top-level feature?
-
- - Yes
- - https://jenkins.opendaylight.org/releng/view/bgpcep/job/bgpcep-csit-1node-periodic-bgp-ingest-mixed-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/bgpcep/job/bgpcep-csit-1node-periodic-bgp-ingest-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/bgpcep/job/bgpcep-csit-1node-periodic-throughpcep-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/bgpcep/job/bgpcep-csit-1node-userfeatures-all-oxygen/
-
-7. Do you have any CLM violations? (Yes/No)
-
- - No
-
-**Stable Features (Only for Projects with Stable Features)**
-
-A. Do your stable features fulfill quality requirements [3]_?
-
- - Yes.
- - https://sonar.opendaylight.org/dashboard?id=org.opendaylight.bgpcep%3Abgpcep-aggregator.
-
-B. Are you running several automated system test jobs [4]_ for each stable
- feature? (Yes/No)
-
- - Yes
- - https://jenkins.opendaylight.org/releng/view/bgpcep/
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance, longevity/stability
+++ /dev/null
-====
-BIER
-====
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts?
-
- - No
-
-2. Has your project met code freeze [1]_?
-
- - Yes
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation?
-
- - Yes
-
-4. Is your documentation complete [2]_?
-
- - Yes
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/bier-user-guide.rst
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/bier-developer-guide.rst
-
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully?
-
- - Yes
-
-6. Are you running at least one basic automated system test job for each
- top-level feature?
-
- - Yes
- - https://jenkins.opendaylight.org/releng/view/bier/job/bier-csit-1node-basic-all-oxygen/
-
-
-7. Do you have any CLM violations? (Yes/No)
-
- - No
-
-**Stable Features (Only for Projects with Stable Features)**
-
-A. Do your stable features fulfill quality requirements [3]_?
-
- - Yes.
- - https://sonar.opendaylight.org/dashboard?id=org.opendaylight.bier%3Abier.
-
-B. Are you running several automated system test jobs [4]_ for each stable
- feature? (Yes/No)
-
- - Yes
- - https://jenkins.opendaylight.org/releng/view/bier/
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance, longevity/stability
+++ /dev/null
-===
-Coe
-===
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts?
-
- No
-
-2. Has your project met code freeze [1]_?
-
- Yes
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation?
-
- Yes
-
-4. Is your documentation complete [2]_?
-
- Yes.
-
- - https://git.opendaylight.org/gerrit/#/c/66869/
- - https://wiki.opendaylight.org/view/COE:Main
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? (No Deliverables/Yes/No)
-
- No. the followings features are postponed to fluorine cycle.
- - k8s service implementation
-
-6. Are you running at least one basic automated system test job for each
- top-level feature?
-
- Coe project has just achieved one end to end functionality implementation in Oxygen.
- CSIT activities have started, and in progress.
- - https://git.opendaylight.org/gerrit/#/c/67227/
-
-7. Do you have any CLM violations?
-
- - https://jenkins.opendaylight.org/releng/view/CLM/job/coe-maven-clm-oxygen/
- - Violations seen are due to other projects Coe depend on, none added by Coe itself.
-
-**Stable Features (Only for Projects with Stable Features)**
-
-A. Do your stable features fulfill quality requirements [3]_?
-
- N/A
-
-B. Are you running several automated system test jobs [4]_ for each stable
- feature?
- N/A
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance,
- longevity/stability
+++ /dev/null
-==========
-Controller
-==========
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project met code freeze [1]_? Yes
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation? Yes
-
-4. Is your documentation complete [2]_? Yes
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Are you running at least one basic automated system test job for each
- top-level feature? Yes
-
- - https://jenkins.opendaylight.org/releng/view/controller/
-
-7. Do you have any CLM violations? No
-
-**Stable Features (Only for Projects with Stable Features)**
-
-A. Do your stable features fulfill quality requirements [3]_? Yes
-
- - https://sonar.opendaylight.org/dashboard?id=org.opendaylight.controller%3Areleasepom
-
-B. Are you running several automated system test jobs [4]_ for each stable
- feature? Yes
-
- - https://jenkins.opendaylight.org/releng/view/controller/
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance,
- longevity/stability
+++ /dev/null
-.. Instructions
-.. 1. Replace Project Name with your actual project name, ensure you have
-.. the same number of ='s as the length of your project in the line before
-.. and the line after.
-.. 2. Remove the (Yes/No) answer at the end of each question with your actual
-.. response: Yes or No
-.. Note: For Question 5, the response could be: No Deliverables
-.. 3. For detailed information on each question, use a sub list with a -
-.. in front that aligns with the text above and ensure you have a blank
-.. line before it.
-..
-
-======
-DAEXIM
-======
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts?
-
- - No
-
-2. Has your project met code freeze [1]_?
-
- - Yes
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation?
-
- - Yes
-
-4. Is your documentation complete [2]_?
-
- - Yes
- - Developer's Guide: https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/daexim-developer-guide.rst;h=301e9bf2a362217eff5b47b7aebcfc0e70fa555b;hb=HEAD
- - User Guide: https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/daexim-user-guide.rst;h=794455c6125bfee5e78983180811ba4f1dae3b6c;hb=HEAD
-
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully?
-
- - No Deliverables
-
-6. Are you running at least one basic automated system test job for each
- top-level feature?
-
- - Yes
- - Jenkins CI for daexim: https://jenkins.opendaylight.org/releng/view/daexim/
-
-7. Do you have any CLM violations?
-
- - No. All warnings and errors are from other projects.
- - https://jenkins.opendaylight.org/releng/view/daexim/job/daexim-maven-clm-oxygen/
-
-**Stable Features (Only for Projects with Stable Features)**
-
-A. Do your stable features fulfill quality requirements [3]_?
-
- - N/A. Not a stable feature.
- - Anyway, sonar is run with 84% Line Coverage and 0 FindBugs.
- - https://jenkins.opendaylight.org/releng/view/All-Sonar/
-
-B. Are you running several automated system test jobs [4]_ for each stable
- feature?
-
- - N/A
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance,
- longevity/stability
+++ /dev/null
-========================
-Integration/Distribution
-========================
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project met code freeze [1]_? Yes
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation? Yes
-
-4. Is your documentation complete [2]_? Yes
-
- - :doc:`../../../user-guide/distribution-version-user-guide`
- - :doc:`../../../developer-guide/distribution-version`
- - :doc:`../../../developer-guide/distribution-test-features`
- - :doc:`../../../getting-started-guide/common-features/clustering`
- - :doc:`../../../getting-started-guide/common-features/persistence_and_backup`
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Are you running at least one basic automated system test job for each
- top-level feature? Yes
-
- - https://jenkins.opendaylight.org/releng/view/distribution
-
-7. Do you have any CLM violations? Yes
-
- - The CLM job reports every violation from upstream
- OpenDaylight projects pulled in by Distribution.
- Those violations should be addressed by upstream projects themselves.
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance,
- longevity/stability
+++ /dev/null
-====
-DLUX
-====
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project met code freeze [1]_? Yes
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation? Yes
-
-4. Is your documentation complete [2]_? Yes
-
- - Developer Guide https://git.opendaylight.org/gerrit/#/c/63280/
- - Release Notes https://git.opendaylight.org/gerrit/#/c/63284/
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? (No Deliverables)
-
-6. Are you running at least one basic automated system test job for each
- top-level feature? No
-
- - https://git.opendaylight.org/gerrit/#/c/29612/
- Outdated patch and due lack of developers we are not working on it.
-
-7. Do you have any CLM violations? (Yes/No)
-
- - Security issues with Angular 1.4.14
- Outdated version of AngularJS. Upgrade to 1.6 version needs some dev and testing time we don't have.
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance,
- longevity/stability
+++ /dev/null
-========
-DLUXApps
-========
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project met code freeze [1]_? Yes
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation? Yes
-
-4. Is your documentation complete [2]_? Yes
-
- - Developer Guide https://git.opendaylight.org/gerrit/#/c/63280/
- - Release Notes https://git.opendaylight.org/gerrit/#/c/63280/
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? (No Deliverables)
-
-6. Are you running at least one basic automated system test job for each
- top-level feature? Yes
-
- - https://jenkins.opendaylight.org/releng/view/dluxapps/job/dluxapps-csit-1node-yangman-all-oxygen/
-
-7. Do you have any CLM violations? (Yes/No)
-
- - Security issues with Angular 1.4.14
- Outdated version of AngularJS. Upgrade to 1.6 version needs some dev and testing time we don't have.
-
- - Everything else came with other projects
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance,
- longevity/stability
+++ /dev/null
-======
-GENIUS
-======
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project met code freeze [1]_? No
-
- - Some patches for new feature 'ITM Scale Improvements' are under review.
- - We plan to get them in before RC1
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation? Yes
-
-4. Is your documentation complete [2]_? Yes
-
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/genius-user-guide.rst;h=1385ebb30901336ff50cf3a1fcc161cd72fd5c8d;hb=HEAD
- - https://git.opendaylight.org/gerrit/gitweb?p=genius.git;a=blob;f=docs/genius-design-doc.rst;h=ce6a41cf56ecf698a5a81da41ac455442fa65f42;hb=HEAD
- - https://git.opendaylight.org/gerrit/gitweb?p=genius.git;a=blob;f=docs/interface-manager-design.rst;h=0fe65872956dd373356dc3aa538b163b82e77a70;hb=HEAD
- - https://git.opendaylight.org/gerrit/gitweb?p=genius.git;a=blob;f=docs/ITM-design.rst;h=e9f740f0e708845462ea41e2d6ae41202d0ada8f;hb=HEAD
- - https://git.opendaylight.org/gerrit/gitweb?p=genius.git;a=tree;f=docs/specs;h=eeaaeb58587345c8de217ca42972f6ad7d10b264;hb=HEAD
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Are you running at least one basic automated system test job for each
- top-level feature? Yes
-
- - https://jenkins.opendaylight.org/releng/view/genius/job/genius-csit-1node-gate-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/genius/job/genius-csit-1node-upstream-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/genius/job/genius-csit-3node-gate-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/genius/job/genius-csit-3node-upstream-all-oxygen/
-
-7. Do you have any CLM violations? No
-
- - https://jenkins.opendaylight.org/releng/view/CLM/job/genius-maven-clm-oxygen/
- - Violations seen are due to other projects Genius depend on, none added
- by Genius itself.
-
-**Stable Features (Only for Projects with Stable Features)**
-
-A. Do your stable features fulfill quality requirements [3]_? NA
-
-
-B. Are you running several automated system test jobs [4]_ for each stable
- feature? NA
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance,
- longevity/stability
+++ /dev/null
-================
-Groupbasedpolicy
-================
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project met code freeze [1]_? Yes
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation? Yes
-
-4. Is your documentation complete [2]_? Yes
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Are you running at least one basic automated system test job for each
- top-level feature? Yes
-
- - https://jenkins.opendaylight.org/releng/view/groupbasedpolicy/job/groupbasedpolicy-csit-1node-3-node-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/groupbasedpolicy/job/groupbasedpolicy-csit-1node-6node-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/groupbasedpolicy/job/groupbasedpolicy-csit-1node-sxp-only-oxygen/
- - https://jenkins.opendaylight.org/releng/view/groupbasedpolicy/job/groupbasedpolicy-csit-3node-clustering-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/groupbasedpolicy/job/groupbasedpolicy-csit-1node-3-node-all-oxygen/
-
-7. Do you have any CLM violations? No
-
-**Stable Features (Only for Projects with Stable Features)**
-
-A. Do your stable features fulfill quality requirements [3]_? N/A
-B. Are you running several automated system test jobs [4]_ for each stable
- feature? N/A
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance,
- longevity/stability
+++ /dev/null
-=============
-Honeycomb/VBD
-=============
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project met code freeze [1]_? Yes
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation? Yes
-
-4. Is your documentation complete [2]_? Yes
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Are you running at least one basic automated system test job for each
- top-level feature? No
-
- - no stable features yet, all are marked as experimental
-
-7. Do you have any CLM violations? No
-
-**Stable Features (Only for Projects with Stable Features)**
-
-A. Do your stable features fulfill quality requirements [3]_? N/A
-B. Are you running several automated system test jobs [4]_ for each stable
- feature? N/A
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance,
- longevity/stability
+++ /dev/null
-==========
-Infrautils
-==========
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project met code freeze [1]_? Yes
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation? Yes
-
-4. Is your documentation complete [2]_? Yes
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Are you running at least one basic automated system test job for each
- top-level feature? Yes
-
- - https://jenkins.opendaylight.org/releng/view/infrautils/
-
-7. Do you have any CLM violations? No
-
-**Stable Features (Only for Projects with Stable Features)**
-
-A. Do your stable features fulfill quality requirements [3]_? Yes
-
- - https://sonar.opendaylight.org/dashboard?id=org.opendaylight.infrautils%3Areleasepom
-
-B. Are you running several automated system test jobs [4]_ for each stable
- feature? Yes
-
- - We do run netvirt csit, since netvirt and genius are the major consumers for our utilities.
- - https://jenkins.opendaylight.org/releng/view/infrautils/
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance,
- longevity/stability
+++ /dev/null
-========
-JSON-RPC
-========
-
-1. Yes, Item 8, M3 - build in autorelease. Pending merge on:
- https://git.opendaylight.org/gerrit/#/c/68055/
- https://git.opendaylight.org/gerrit/#/c/68054/
- https://git.opendaylight.org/gerrit/#/c/67788/
- 67788 should be green after the other two are merged.
-
-2. Has your project met code freeze?
- Yes.
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation? Yes
-
-4. Is your documentation complete? Yes
-
- - All docs in M3 report
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Are you running at least one basic automated system test job for each
- top-level feature? No
-
- - We need to add CIT one of the 3rd party JSON RPC stacks (either perl or
- python for CIT tests). Until this is done we can do only unit tests.
-
-7. Do you have any CLM violations? (Yes/No)
-
- - Yes. The report on Nexus is not up to date, judging by versions it is
- for Nitrogen. Analyzing by hand none of the dependencies listed there
- are present in the Oxygen build. We will be clear where we stand there
- once the pending merges into dist-check and autorelease are complete
- and the job is re-ran.
-
-**Stable Features (Only for Projects with Stable Features)**
-
-A. Do your stable features fulfill quality requirements? (Yes/No)
-
- - N/A
-
-B. Are you running several automated system test jobs for each stable
- feature? (Yes/No)
-
- - N/A
-
+++ /dev/null
-========
-L2Switch
-========
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? *No*
-
-2. Has your project met code freeze [1]_? *Yes*
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation? *Yes*
-
-4. Is your documentation complete [2]_? *Yes*
-
- - User Guide [5]_
- - Developer Guide [6]_
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? *No Deliverables*
-
-6. Are you running at least one basic automated system test job for each
- top-level feature? *Yes*
-
- - Test Report [7]_
-
-7. Do you have any CLM violations? *No*
-
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance,
- longevity/stability
-.. [5] https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/l2switch-user-guide.rst;h=381e9f9b3b3e5e6a072af58d011f5f23411f6b95;hb=refs/heads/master
-.. [6] https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/l2switch-developer-guide.rst;h=96d7789d80c3597a10a276e9a17c0796b62634d6;hb=refs/heads/master
-.. [7] https://jenkins.opendaylight.org/releng/view/l2switch/job/l2switch-csit-1node-switch-all-oxygen/
-
+++ /dev/null
-=================
-LISP Flow Mapping
-=================
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project met code freeze [1]_? Yes
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation? Yes
-
-4. Is your documentation complete [2]_? Yes
-
- - There is one outstanding patch that needs to merge only after stable
- branch cutting: https://git.opendaylight.org/gerrit/#/c/67234/
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? Yes
-
-6. Are you running at least one basic automated system test job for each
- top-level feature? (Yes/No)
-
- - https://jenkins.opendaylight.org/releng/view/lispflowmapping/job/lispflowmapping-csit-1node-msmr-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/lispflowmapping/job/lispflowmapping-csit-3node-msmr-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/lispflowmapping/job/lispflowmapping-csit-1node-performance-only-oxygen/
-
-7. Do you have any CLM violations? No
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance,
- longevity/stability
+++ /dev/null
-====
-NEMO
-====
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project met code freeze [1]_? Yes
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation? Yes
-
-4. Is your documentation complete [2]_? Yes
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Are you running at least one basic automated system test job for each
- top-level feature? Yes
-
- - https://jenkins.opendaylight.org/releng/view/nemo/
-
-7. Do you have any CLM violations? No
-
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance,
- longevity/stability
+++ /dev/null
-=======
-Netconf
-=======
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project met code freeze [1]_? Yes
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation? Yes
-
-4. Is your documentation complete [2]_? Yes
-
- - Documentation from the previous release still applies.
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Are you running at least one basic automated system test job for each
- top-level feature? Yes
-
- - https://jenkins.opendaylight.org/releng/view/netconf/
-
-7. Do you have any CLM violations? Yes
-
- - There are violations with outdated versions of jackson-databind and
- ehcache components. We don't dev time to test and update newer
- versions of the components.
-
-**Stable Features (Only for Projects with Stable Features)**
-
-A. Do your stable features fulfill quality requirements [3]_? No
-
- - We might not have that high UT coverage for each stable feature. But
- we have exhaustive CSIT tests for stable feature.
-
-B. Are you running several automated system test jobs [4]_ for each stable
- feature? Yes
-
- - https://jenkins.opendaylight.org/releng/view/netconf/
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance,
- longevity/stability
+++ /dev/null
-=======
-NetVirt
-=======
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project met code freeze [1]_? No
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation? Yes
-
-4. Is your documentation complete [2]_? Yes
-
- - :doc:`../../submodules/netvirt/docs/user-guide/index`
- - :doc:`../../submodules/netvirt/docs/openstack-guide/index`
- - :doc:`../../submodules/netvirt/docs/developer-guide/index`
- - :doc:`../../submodules/netvirt/docs/contributor-guide/index`
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Are you running at least one basic automated system test job for each
- top-level feature? Yes
-
- - https://jenkins.opendaylight.org/releng/view/netvirt-csit/
-
-7. Do you have any CLM violations? No
-
- - https://jenkins.opendaylight.org/releng/view/CLM/job/netvirt-maven-clm-oxygen/
- - Violations seen are due to other projects NetVirt depends on, none added
- by Genius itself.
+++ /dev/null
-.. Instructions
-.. 1. Replace Project Name with your actual project name, ensure you have
-.. the same number of ='s as the length of your project in the line before
-.. and the line after.
-.. 2. Remove the (Yes/No) answer at the end of each question with your actual
-.. response: Yes or No
-.. Note: For Question 5, the response could be: No Deliverables
-.. 3. For detailed information on each question, use a sub list with a -
-.. in front that aligns with the text above and ensure you have a blank
-.. line before it.
-..
-
-==================
-Neutron Northbound
-==================
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts?
-
- No
-
-2. Has your project met code freeze [1]_?
-
- Yes
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation?
-
- Yes
-
-4. Is your documentation complete [2]_?
-
- Yes. No update since Nitrgen cycle.
-
- - (For each document, link to the file in gerrit)
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/neutron-northbound.rst;hb=HEAD
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/neutron-service-developer-guide.rst;hb=HEAD
- - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/neutron-service-user-guide.rst;hb=HEAD
-
- - (Link to pending gerrit patches waiting approval)
- - None
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? (No Deliverables/Yes/No)
-
- No. the followings features are postponed to fluorine cycle.
- - removal of tenant-id
- - move status from configuration space to operation space
- - port status update
-
-6. Are you running at least one basic automated system test job for each
- top-level feature?
-
- - (If yes, link to test report)
- - (If not, explain why)
-
- No. System test waiver is applied.
- - https://lists.opendaylight.org/pipermail/release/2017-October/012703.html
- Yes with OpenStack CI.
- - https://review.openstack.org/#/q/project:openstack/networking-odl
-
- Also ODL Neutron Northbound is tested with NetVirt project, OPNFV FastDataStack
-
-7. Do you have any CLM violations?
-
- - (If yes, list your CLM violations and explain why each violation can be exempt)
-
- Yes as shown by NEUTRON CLM job.
- - https://clm.opendaylight.org/assets/index.html#/reports/neutron/5fc334cf335a41659786db11e8d5e67e
-
- In short, Neutron Northbound uses some of them and the fix should
- be to upgrade their versions. But all the versions are specified by
- odlparent or dependent projects.
-
-**Stable Features (Only for Projects with Stable Features)**
-
-N/A
-
-A. Do your stable features fulfill quality requirements [3]_?
-
- - (If yes, link to sonar report)
- - (If not, explain why)
-
- N/A
-
-B. Are you running several automated system test jobs [4]_ for each stable
- feature?
-
- - (If yes, link to test reports)
- - (If not, explain why)
-
- N/A
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance,
- longevity/stability
+++ /dev/null
-==========
-ODL Parent
-==========
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project met code freeze? Yes
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation? Yes
-
-4. Is your documentation complete? No
-
- - Developer's Guide: https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/odl-parent-developer-guide.rst
- - Updates forthcoming for 3.0
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? Yes
-
-6. Are you running at least one basic automated system test job for each
- top-level feature? No
-
- - ODL Parent has a system test waiver
-
-7. Do you have any CLM violations? (Yes/No)
-
- - Yes. The newly-identified vulnerabilities are as follows:
-
- - ``org.apache.karaf.jaas.modules``: this is a false-positive based on
- httpcomponents but using the Karaf version
- - CVE-2016-3092, CVE-1026-1000031: file upload in Karaf; this isn’t
- exposed in ODL
- - ``org.ops4j.pax.web`` JSP vulnerabilities: ODL doesn’t ship any JSPs
-
-**Stable Features (Only for Projects with Stable Features)**
-
-A. Do your stable features fulfill quality requirements? No
-
- - ODL Parent’s features wrap upstream features, so they rely on upstream’s
- testing
-
-B. Are you running several automated system test jobs for each stable
- feature? No
-
- - ODL Parent has a system test waiver
+++ /dev/null
-=========
-OF-CONFIG
-=========
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project met code freeze [1]_? Yes
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation? Yes
-
-4. Is your documentation complete [2]_? Yes
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Are you running at least one basic automated system test job for each
- top-level feature? Yes
-
- - https://jenkins.opendaylight.org/releng/view/of-config/job/of-config-csit-1node-basic-all-oxygen/
-
-7. Do you have any CLM violations? No
-
-**Stable Features (Only for Projects with Stable Features)**
-
-A. Do your stable features fulfill quality requirements [3]_? (Yes/No)
-
- - (If yes, link to sonar report)
- - (If not, explain why)
-
-B. Are you running several automated system test jobs [4]_ for each stable
- feature? (Yes/No)
-
- - (If yes, link to test reports)
- - (If not, explain why)
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance,
- longevity/stability
+++ /dev/null
-===============
-OpenFlow Plugin
-===============
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project met code freeze [1]_? Yes
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation? Yes
-
-4. Is your documentation complete [2]_? Yes
-
- * **User Guide(s):**
-
- * :doc:`../../../user-guide/openflow-plugin-project-user-guide`
-
- * **Developer Guide(s):**
-
- * :doc:`../../../developer-guide/openflow-plugin-project-developer-guide`
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? Yes
-
-6. Are you running at least one basic automated system test job for each
- top-level feature? Yes
-
- - ` CSIT Tests <https://jenkins.opendaylight.org/releng/view/openflowplugin/>`_
-
-7. Do you have any CLM violations?
-
- - All violations are transitive dependencies from other ODL Projects
-
-**Stable Features (Only for Projects with Stable Features)**
-
-A. Do your stable features fulfill quality requirements [3]_? Yes
- Almost (Main plugin implementation has coverage more than 75%. Overall Unit Test Coverage is 68%, but we have
- extensive CSIT that overall increase the coverage above 75%)
-
- - https://sonar.opendaylight.org/dashboard?id=org.opendaylight.openflowplugin%3Aopenflowplugin-impl
-
-B. Are you running several automated system test jobs [4]_ for each stable
- feature? Yes, please refer the below URL to see details of all the running CSIT jobs.
-
- - ` CSIT Tests <https://jenkins.opendaylight.org/releng/view/openflowplugin/>`_
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance,
- longevity/stability
+++ /dev/null
-======
-OpFlex
-======
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project met code freeze? Yes
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation? Yes
-
-4. Is your documentation complete? Yes
-
- - ./docs/developer-guide/opflex-libopflex-developer-guide.rst
- - ./docs/developer-guide/opflex-agent-ovs-developer-guide.rst
- - ./docs/developer-guide/opflex-genie-developer-guide.rst
- - ./docs/user-guide/opflex-agent-ovs-user-guide.rst
- - ./docs/getting-started-guide/project-specific-guides/opflex.rst
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Are you running at least one basic automated system test job for each
- top-level feature? N/A
-
-7. Do you have any CLM violations? N/A
+++ /dev/null
-=====
-OVSDB
-=====
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project met code freeze [1]_? Yes
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation? Yes
-
-4. Is your documentation complete [2]_? Yes
-
- - Developer's Guide: https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/ovsdb-developer-guide.rst
- - User's Guide: https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/ovsdb-user-guide.rst
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables (bug fixes only)
-
-6. Are you running at least one basic automated system test job for each
- top-level feature? (Yes/No)
-
- - ` CSIT Tests <https://jenkins.opendaylight.org/releng/view/ovsdb/>`_
-
-7. Do you have any CLM violations?
-
- - All violations are transitice dependencies from other ODL Projects
-
-**Stable Features (Only for Projects with Stable Features)**
-
-A. Do your stable features fulfill quality requirements [3]_? N.A.
-
-B. Are you running several automated system test jobs [4]_ for each stable
- feature? N.A.
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance,
- longevity/stability
+++ /dev/null
-=========
-P4 Plugin
-=========
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? Yes, we are busy with automated system test now.
-
-2. Has your project met code freeze [1]_? Yes
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation? Yes
-
-4. Is your documentation complete [2]_? Yes
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Are you running at least one basic automated system test job for each
- top-level feature? Yes
-
- - https://jenkins.opendaylight.org/releng/view/p4plugin/job/p4plugin-csit-1node-basic-all-oxygen/
-
-7. Do you have any CLM violations? No
-
-**Stable Features (Only for Projects with Stable Features)**
-
-A. Do your stable features fulfill quality requirements [3]_? (Yes/No)
-
- - (If yes, link to sonar report)
- - (If not, explain why)
-
-B. Are you running several automated system test jobs [4]_ for each stable
- feature? (Yes/No)
-
- - (If yes, link to test reports)
- - (If not, explain why)
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance,
- longevity/stability
+++ /dev/null
-===========
-Packetcable
-===========
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts?
- No
-
-2. Has your project met code freeze?
- Yes
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation?
- Yes
-
-4. Is your documentation complete?
- Yes
-
- - packetcable-user-guide.rst:
- https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/packetcable-user-guide.rst;h=4454d4aaa69337917dfa3fd0593f8b358b8823e6;hb=refs/heads/master
-
- - packetcable-developer-guide.rst:
- https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/packetcable-developer-guide.rst;h=e7255fc1ec843122650cbb69e45bd96629bbcb3f;hb=refs/heads/master
-
- - No pending gerrit patches are waiting approval
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully?
- Yes
-
-6. Are you running at least one basic automated system test job for each
- top-level feature?
- Yes
-
- - https://jenkins.opendaylight.org/releng/view/packetcable/job/packetcable-csit-1node-pcmm-all-oxygen/131/robot/
-
-7. Do you have any CLM violations?
- Yes
-
- - Violations are in upstream components.
-
-
-**Stable Features (Only for Projects with Stable Features)**
-
-** The Packetcable project has no stable features. **
-
-A. Do your stable features fulfill quality requirements [3]_? (Yes/No)
-
-B. Are you running several automated system test jobs [4]_ for each stable
- feature? (Yes/No)
-
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance,
- longevity/stability
+++ /dev/null
-
-=========================
-Service Function Chaining
-=========================
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project met code freeze [1]_? Yes, on January 31, 2018.
- The CSIT infrastructure changes introduced in the middle of the
- release caused serious problems for SFC, consequently, we were
- late reaching this milestone. We worked with the Linux Foundation
- on a solution, and were finally able to reach a solution on Monday,
- January 29, 2018, at which time we submit the following integration
- test patches:
-
- - https://git.opendaylight.org/gerrit/#/c/67539/ Merged January 29, 2018
- - https://git.opendaylight.org/gerrit/#/c/67544/ Merged January 29, 2018
-
- Once these integration/test patches were merged, we had to verify CSIT
- on the following pending SFC patches, since it had not been possible
- to do so until now:
-
- - https://git.opendaylight.org/gerrit/65007
- - https://git.opendaylight.org/gerrit/66750
- - https://git.opendaylight.org/gerrit/67127
- - https://git.opendaylight.org/gerrit/67585
- - https://git.opendaylight.org/gerrit/67432
- - https://git.opendaylight.org/gerrit/66956
-
- All of these SFC patches were merged by Wednesday, January 31, 2018.
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation? Yes
-
-4. Is your documentation complete [2]_? No
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Are you running at least one basic automated system test job for each
- top-level feature? Yes
-
- - https://jenkins.opendaylight.org/releng/view/sfc/
-
-7. Do you have any CLM violations? No
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance,
- longevity/stability
+++ /dev/null
-.. Instructions
-.. 1. Replace Project Name with your actual project name, ensure you have
-.. the same number of ='s as the length of your project in the line before
-.. and the line after.
-.. 2. Remove the (Yes/No) answer at the end of each question with your actual
-.. response: Yes or No
-.. Note: For Question 5, the response could be: No Deliverables
-.. 3. For detailed information on each question, use a sub list with a -
-.. in front that aligns with the text above and ensure you have a blank
-.. line before it.
-..
-
-====
-Snmp
-====
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project met code freeze [1]_? Yes
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation? Yes
-
-4. Is your documentation complete [2]_? Yes
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Are you running at least one basic automated system test job for each
- top-level feature? No
-
- - (If not, explain why) No test jobs have been developed
-
-7. Do you have any CLM violations? No
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance,
- longevity/stability
+++ /dev/null
-========
-SNMP4SDN
-========
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project met code freeze [1]_? Yes
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation? Yes
-
-4. Is your documentation complete [2]_? Yes
-
- - (For each document, link to the file in gerrit)
- - https://git.opendaylight.org/gerrit/#/c/44354/
- - https://git.opendaylight.org/gerrit/#/c/44189/
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Are you running at least one basic automated system test job for each
- top-level feature? No
-
- - System test waiver
-
-7. Do you have any CLM violations? No
-
-
-**Stable Features (Only for Projects with Stable Features)**
-
-A. Do your stable features fulfill quality requirements [3]_? No
-
- - Left for future work
-
-B. Are you running several automated system test jobs [4]_ for each stable
- feature? No
-
- - System test waiver
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance,
- longevity/stability
+++ /dev/null
-===
-SXP
-===
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project met code freeze [1]_? Yes
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation? Yes
-
-4. Is your documentation complete [2]_? Yes
-
- - Developer docs - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/sxp-developer-guide.rst;h=020eae563872c7c292eeebe5893068ae85935f05;hb=HEAD
- - User guide - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/sxp-user-guide.rst;h=ea2ce60ed85c9be80e9049260492e33814c34ab5;hb=HEAD
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Are you running at least one basic automated system test job for each
- top-level feature? Yes
-
- - https://jenkins.opendaylight.org/releng/view/sxp/job/sxp-csit-1node-basic-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/sxp/job/sxp-csit-1node-filtering-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/sxp/job/sxp-csit-1node-periodic-performance-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/sxp/job/sxp-csit-1node-topology-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/sxp/job/sxp-csit-3node-periodic-clustering-all-oxygen/
- - https://jenkins.opendaylight.org/releng/view/sxp/job/sxp-csit-3node-periodic-routing-all-oxygen/
-
-7. Do you have any CLM violations? (Yes/No)
-
- - All the violations present are either transitive dependencies from other ODL projects, or are used
- solely for testing.
-
-**Stable Features (Only for Projects with Stable Features)**
-
-A. Do your stable features fulfill quality requirements [3]_? No stable features
-
-
-B. Are you running several automated system test jobs [4]_ for each stable
- feature? No stable features
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance,
- longevity/stability
+++ /dev/null
-====
-TSDR
-====
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project met code freeze [1]_? Yes
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation? Yes
-
-4. Is your documentation complete [2]_? Yes
-
- - TSDR User Guide [5]_
- - TSDR ElasticSearch User Guide [6]_
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Are you running at least one basic automated system test job for each
- top-level feature? Yes
-
- - https://jenkins.opendaylight.org/releng/view/tsdr/
-
-7. Do you have any CLM violations? No
-
-**Stable Features (Only for Projects with Stable Features)**
-
-A. Do your stable features fulfill quality requirements [3]_? No
-
- - TSDR coverage has slipped due to changes in the framework. We are
- working to fix the test cases that are broken.
- - https://sonar.opendaylight.org/dashboard?id=org.opendaylight.tsdr%3Areleasepom [7]_
-
-B. Are you running several automated system test jobs [4]_ for each stable
- feature? Yes
-
- - https://jenkins.opendaylight.org/releng/view/tsdr/
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance,
- longevity/stability
-.. [5] https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/tsdr-user-guide.rst
-.. [6] https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/tsdr-elastic-search.rst
-.. [7] TSDR needs to be added back to distribution. We are looking into it.
+++ /dev/null
-===
-USC
-===
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project met code freeze [1]_? Yes
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation? Yes
-
-4. Is your documentation complete [2]_? Yes
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Are you running at least one basic automated system test job for each
- top-level feature? Yes
-
- - https://jenkins.opendaylight.org/releng/view/usc/
-
-7. Do you have any CLM violations? No
-
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance,
- longevity/stability
+++ /dev/null
-===
-VTN
-===
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? No
-
-2. Has your project met code freeze [1]_? Yes
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation? Yes
-
-4. Is your documentation complete [2]_? Yes
-
- - User's Guide: https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/virtual-tenant-network-(vtn).rst
- - Developer's Guide: https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/virtual-tenant-network-(vtn).rst
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? No Deliverables
-
-6. Are you running at least one basic automated system test job for each
- top-level feature? Yes
-
- - https://jenkins.opendaylight.org/releng/view/vtn/
-
-7. Do you have any CLM violations? No
-
-**Stable Features (Only for Projects with Stable Features)**
-
-A. Do your stable features fulfill quality requirements [3]_? Yes
-
- - https://sonar.opendaylight.org/dashboard?id=org.opendaylight.vtn%3Adistribution
-
-B. Are you running several automated system test jobs [4]_ for each stable
- feature? Yes
-
- - https://jenkins.opendaylight.org/releng/view/vtn/
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance,
- longevity/stability
-
+++ /dev/null
-.. Instructions
-.. 1. Replace Project Name with your actual project name, ensure you have
-.. the same number of ='s as the length of your project in the line before
-.. and the line after.
-.. 2. Remove the (Yes/No) answer at the end of each question with your actual
-.. response: Yes or No
-.. Note: For Question 5, the response could be: No Deliverables
-.. 3. For detailed information on each question, use a sub list with a -
-.. in front that aligns with the text above and ensure you have a blank
-.. line before it.
-..
-
-============
-Project Name
-============
-
-1. Do you have any previously-incomplete items from prior milestone
- readouts? (Yes/No)
-
-2. Has your project met code freeze [1]_? (Yes/No)
-
-3. Are all externally visible strings frozen to allow for translation &
- documentation? (Yes/No)
-
-4. Is your documentation complete [2]_? (Yes/No)
-
- - (For each document, link to the file in gerrit)
- - (Link to pending gerrit patches waiting approval)
-
-5. Were project-specific deliverables planned for this milestone delivered
- successfully? (No Deliverables/Yes/No)
-
-6. Are you running at least one basic automated system test job for each
- top-level feature? (Yes/No)
-
- - (If yes, link to test report)
- - (If not, explain why)
-
-7. Do you have any CLM violations? (Yes/No)
-
- - (If yes, list your CLM violations and explain why each violation can be exempt)
-
-**Stable Features (Only for Projects with Stable Features)**
-
-A. Do your stable features fulfill quality requirements [3]_? (Yes/No)
-
- - (If yes, link to sonar report)
- - (If not, explain why)
-
-B. Are you running several automated system test jobs [4]_ for each stable
- feature? (Yes/No)
-
- - (If yes, link to test reports)
- - (If not, explain why)
-
-.. [1] Only bug fixes are allowed from now on
-.. [2] Only editing and enhancing should take place from now on
-.. [3] Unit and/or integration test coverage of at least 75%
-.. [4] These test jobs include functionality, cluster, scalability, performance,
- longevity/stability
+++ /dev/null
-===\r
-AAA\r
-===\r
-\r
-1. Gerrit patch for release notes of this major release:\r
-\r
- - https://git.opendaylight.org/gerrit/#/c/69679\r
-\r
-2. Have you tested the latest release candidate? Yes\r
-\r
- - No issues found\r
-\r
-3. Do you have CSIT failures associated with the latest release candidate? Yes\r
-\r
- - Updated tracking spreadsheet for failures: Yes\r
-\r
-4. Do you plan to address CLM violations applicable to your project\r
- post-release? Yes\r
-\r
-5. Do you approve making the latest release candidate the official Opendaylight\r
- release? Yes\r
-\r
-6. Feedback on this release:\r
-\r
- - None\r
+++ /dev/null
-===========\r
-BGP LS PCEP\r
-===========\r
-\r
-1. Gerrit patch for release notes of this major release:\r
-\r
- - https://git.opendaylight.org/gerrit/#/c/69255/\r
-\r
-2. Have you tested the latest release candidate?\r
-\r
- - No issues found.\r
-\r
-3. Do you have CSIT failures associated with the latest release candidate?\r
-\r
- - Updated tracking spreadsheet for failures: Yes\r
-\r
-4. Do you plan to address CLM violations applicable to your project\r
- post-release? Not Applicable\r
-\r
-5. Do you approve making the latest release candidate the official Opendaylight\r
- release? Yes\r
-\r
-6. Feedback on this release:\r
-\r
- - None\r
+++ /dev/null
-====\r
-BIER\r
-====\r
-\r
-1. Gerrit patch for release notes of this major release:\r
-\r
- - https://git.opendaylight.org/gerrit/#/c/69514/\r
-\r
-2. Have you tested the latest release candidate?\r
-\r
- - No issues found.\r
-\r
-3. Do you have CSIT failures associated with the latest release candidate?\r
-\r
- - Updated tracking spreadsheet for failures: Not Applicable\r
-\r
-4. Do you plan to address CLM violations applicable to your project\r
- post-release? No\r
-\r
-5. Do you approve making the latest release candidate the official Opendaylight\r
- release? Yes\r
-\r
-6. Feedback on this release:\r
-\r
- - None\r
+++ /dev/null
-===
-COE
-===
-
-1. Gerrit patch for release notes of this major release:
-
- - `COE Release Notes <https://git.opendaylight.org/gerrit/#/c/69253/>`_
-
-2. Have you tested the latest release candidate? Yes
-
- - No issues found
-
-3. Do you have CSIT failures associated with the latest release candidate? No
-
-4. Do you plan to address CLM violations applicable to your project
- post-release? Yes
-
-5. Do you approve making the latest release candidate the official Opendaylight
- release? Yes
-
-6. Feedback on this release:
-
- - None)
+++ /dev/null
-==========\r
-controller\r
-==========\r
-\r
-1. Gerrit patch for release notes of this major release:\r
-\r
- - https://git.opendaylight.org/gerrit/#/c/69239\r
-\r
-2. Have you tested the latest release candidate? Yes\r
-\r
- - No issues found\r
-\r
-3. Do you have CSIT failures associated with the latest release candidate? No blockers\r
-\r
- - Updated tracking spreadsheet for failures: Yes\r
-\r
-4. Do you plan to address CLM violations applicable to your project\r
- post-release? Yes\r
-\r
-5. Do you approve making the latest release candidate the official Opendaylight\r
- release? Yes\r
-\r
-6. Feedback on this release:\r
-\r
- - None\r
+++ /dev/null
-======
-DAEXIM
-======
-
-1. Gerrit patch for release notes of this major release:
-
- - https://git.opendaylight.org/gerrit/#/c/69576/
-
-2. Have you tested the latest release candidate? (Yes/No)
-
- - Yes, via CI only. Manually test not needed as CI tests are comprehensive.
- - No open issues.
-
-3. Do you have CSIT failures associated with the latest release candidate?
-
- - No
- - Updated tracking spreadsheet for failures: Not Applicable
-
-4. Do you plan to address CLM violations applicable to your project
- post-release?
-
- - Not Applicable
-
-5. Do you approve making the latest release candidate the official Opendaylight
- release?
-
- - Yes
-
-6. Feedback on this release:
-
- - None
+++ /dev/null
-====
-Dlux
-====
-
-1. Gerrit patch for release notes of this major release:
-
- - https://git.opendaylight.org/gerrit/#/c/69771/
-
-2. Have you tested the latest release candidate?
-
- - Yes, No issues found
-
-3. Do you have CSIT failures associated with the latest release candidate?
-
- - Updated tracking spreadsheet for failures: Not Applicable
-
-4. Do you plan to address CLM violations applicable to your project
- post-release?
-
- - No
-
-5. Do you approve making the latest release candidate the official Opendaylight
- release?
-
- - Yes
-
-6. Feedback on this release:
-
- - None
+++ /dev/null
-========
-DluxApps
-========
-
-1. Gerrit patch for release notes of this major release:
-
- - https://git.opendaylight.org/gerrit/#/c/69773/
-
-2. Have you tested the latest release candidate?
-
- - Yes
-
-3. Do you have CSIT failures associated with the latest release candidate?
-
- - Updated tracking spreadsheet for failures: Yes
-
-4. Do you plan to address CLM violations applicable to your project
- post-release?
-
- - No
-
-5. Do you approve making the latest release candidate the official Opendaylight
- release?
-
- - Yes
-
-6. Feedback on this release:
-
- - None
+++ /dev/null
-==========
-Infrautils
-==========
-
-1. Gerrit patch for release notes of this major release:
-
- - `Infrautils Release Notes <https://git.opendaylight.org/gerrit/#/c/69251/>`_
-
-2. Have you tested the latest release candidate? Yes
-
- - No issues found
-
-3. Do you have CSIT failures associated with the latest release candidate? No Blockers
-
-4. Do you plan to address CLM violations applicable to your project
- post-release? Yes
-
-5. Do you approve making the latest release candidate the official Opendaylight
- release? Yes
-
-6. Feedback on this release:
-
- - None)
+++ /dev/null
-=================\r
-LISP Flow Mapping\r
-=================\r
-\r
-1. Gerrit patch for release notes of this major release:\r
-\r
- - https://git.opendaylight.org/gerrit/#/c/69666/\r
-\r
-2. Have you tested the latest release candidate? Yes\r
-\r
- - No issues found\r
-\r
-3. Do you have CSIT failures associated with the latest release candidate? Yes\r
-\r
- - Updated tracking spreadsheet for failures: Yes\r
-\r
-4. Do you plan to address CLM violations applicable to your project\r
- post-release? Not Applicable\r
-\r
-5. Do you approve making the latest release candidate the official Opendaylight\r
- release? Yes\r
-\r
-6. Feedback on this release:\r
-\r
- - None\r
+++ /dev/null
-.. Instructions\r
-.. 1. Replace Project Name with your actual project name, ensure you have\r
-.. the same number of ='s as the length of your project in the line before\r
-.. and the line after.\r
-.. 2. Replace "xyz12" for item 1 with your actual gerrit patch number\r
-.. 3. Remove the (Yes/No) or (Yes/No/Not Applicable) answer at the end of\r
-.. each question with your actual response: Yes, No, Not Applicable\r
-.. 4. For detailed information on each item, use a sub list with a -\r
-.. in front that aligns with the text above and ensure you have a blank\r
-.. line before it.\r
-\r
-====\r
-NEMO\r
-====\r
-\r
-1. Gerrit patch for release notes of this major release:\r
-\r
- - `NEMO Release Notes <https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/release-notes/projects/nemo.rst;>`_\r
-\r
-2. Have you tested the latest release candidate? Yes\r
-\r
- - No issues found\r
-\r
-3. Do you have CSIT failures associated with the latest release candidate? No Blockers\r
-\r
- - Updated tracking spreadsheet for failures: Yes\r
-\r
-4. Do you plan to address CLM violations applicable to your project\r
- post-release? Yes\r
-\r
-5. Do you approve making the latest release candidate the official Opendaylight\r
- release? Yes\r
-\r
-6. Feedback on this release:\r
-\r
- - None\r
+++ /dev/null
-.. Instructions\r
-.. 1. Replace Project Name with your actual project name, ensure you have\r
-.. the same number of ='s as the length of your project in the line before\r
-.. and the line after.\r
-.. 2. Replace "xyz12" for item 1 with your actual gerrit patch number\r
-.. 3. Remove the (Yes/No) or (Yes/No/Not Applicable) answer at the end of\r
-.. each question with your actual response: Yes, No, Not Applicable\r
-.. 4. For detailed information on each item, use a sub list with a -\r
-.. in front that aligns with the text above and ensure you have a blank\r
-.. line before it.\r
-\r
-=======\r
-NETCONF\r
-=======\r
-\r
-1. Gerrit patch for release notes of this major release:\r
-\r
- - https://git.opendaylight.org/gerrit/#/c/69690/\r
-\r
-2. Have you tested the latest release candidate? No\r
-\r
- - We have exhaustive CSIT for that.\r
-\r
-3. Do you have CSIT failures associated with the latest release candidate? Yes\r
-\r
- - Updated tracking spreadsheet for failures: Yes\r
-\r
-4. Do you plan to address CLM violations applicable to your project\r
- post-release? No\r
-\r
-5. Do you approve making the latest release candidate the official Opendaylight\r
- release? Yes\r
-\r
-6. Feedback on this release:\r
-\r
- - None\r
+++ /dev/null
-=======\r
-NetVirt\r
-=======\r
-\r
-1. Gerrit patch for release notes of this major release:\r
-\r
- - `NetVirt Release Notes <https://git.opendaylight.org/gerrit/69557>`_\r
-\r
-2. Have you tested the latest release candidate? Yes\r
-\r
- - No issues found\r
-\r
-3. Do you have CSIT failures associated with the latest release candidate? No Blockers\r
-\r
- - Updated tracking spreadsheet for failures: Yes\r
-\r
-4. Do you plan to address CLM violations applicable to your project\r
- post-release? Yes\r
-\r
-5. Do you approve making the latest release candidate the official Opendaylight\r
- release? Yes\r
-\r
-6. Feedback on this release:\r
-\r
- - None)\r
+++ /dev/null
-.. Instructions
-.. 1. Replace Project Name with your actual project name, ensure you have
-.. the same number of ='s as the length of your project in the line before
-.. and the line after.
-.. 2. Replace "xyz12" for item 1 with your actual gerrit patch number
-.. 3. Remove the (Yes/No) or (Yes/No/Not Applicable) answer at the end of
-.. each question with your actual response: Yes, No, Not Applicable
-.. 4. For detailed information on each item, use a sub list with a -
-.. in front that aligns with the text above and ensure you have a blank
-.. line before it.
-
-==================
-Neutron Northbound
-==================
-
-1. Gerrit patch for release notes of this major release:
-
- - https://git.opendaylight.org/gerrit/#/c/69461/
-
-2. Have you tested the latest release candidate? Yes
-
- - https://review.openstack.org/#/c/552717/
- tested with OpenStack CI
-
-3. Do you have CSIT failures associated with the latest release candidate? No
-
- - Updated tracking spreadsheet for failures: Not Applicable
-
-4. Do you plan to address CLM violations applicable to your project
- post-release? Yes
-
-5. Do you approve making the latest release candidate the official Opendaylight
- release? Yes
-
-6. Feedback on this release:
-
- - None
+++ /dev/null
-=========\r
-OF-CONFIG\r
-=========\r
-\r
-1. Gerrit patch for release notes of this major release:\r
-\r
- - https://git.opendaylight.org/gerrit/#/c/69512/\r
-\r
-2. Have you tested the latest release candidate?\r
-\r
- - No issues found.\r
-\r
-3. Do you have CSIT failures associated with the latest release candidate?\r
-\r
- - Updated tracking spreadsheet for failures: Yes\r
-\r
-4. Do you plan to address CLM violations applicable to your project\r
- post-release? No\r
-\r
-5. Do you approve making the latest release candidate the official Opendaylight\r
- release? Yes\r
-\r
-6. Feedback on this release:\r
-\r
- - None\r
+++ /dev/null
-======\r
-OpFlex\r
-======\r
-\r
-1. Gerrit patch for release notes of this major release:\r
-\r
- - https://git.opendaylight.org/gerrit/#/c/69640/\r
-\r
-2. Have you tested the latest release candidate? Yes\r
-\r
- - No issues found\r
-\r
-3. Do you have CSIT failures associated with the latest release candidate? No\r
-\r
- - Updated tracking spreadsheet for failures: N/A\r
-\r
-4. Do you plan to address CLM violations applicable to your project\r
- post-release? N/A\r
-\r
-5. Do you approve making the latest release candidate the official Opendaylight\r
- release? Yes\r
-\r
-6. Feedback on this release:\r
-\r
- - None\r
+++ /dev/null
-=======
-OVSDB
-=======
-
-1. Gerrit patch for release notes of this major release:
-
- - `OVSDB Release Notes <https://git.opendaylight.org/gerrit/69600>`_
-
-2. Have you tested the latest release candidate? Yes
-
- - No issues found
-
-3. Do you have CSIT failures associated with the latest release candidate? No Blockers
-
- - Updated tracking spreadsheet for failures: Yes
-
-4. Do you plan to address CLM violations applicable to your project
- post-release? Yes
-
-5. Do you approve making the latest release candidate the official Opendaylight
- release? Yes
-
-6. Feedback on this release:
-
- - None)
\ No newline at end of file
+++ /dev/null
-=========\r
-P4 Plugin\r
-=========\r
-\r
-1. Gerrit patch for release notes of this major release:\r
-\r
- - https://git.opendaylight.org/gerrit/#/c/67097/\r
-\r
-2. Have you tested the latest release candidate?\r
-\r
- - No issues found.\r
-\r
-3. Do you have CSIT failures associated with the latest release candidate?\r
-\r
- - Updated tracking spreadsheet for failures: Yes\r
-\r
-4. Do you plan to address CLM violations applicable to your project\r
- post-release? No\r
-\r
-5. Do you approve making the latest release candidate the official Opendaylight\r
- release? Yes\r
-\r
-6. Feedback on this release:\r
-\r
- - None\r
+++ /dev/null
-\r
-===========\r
-Packetcable\r
-===========\r
-\r
-1. Gerrit patch for release notes of this major release:\r
-\r
- - https://git.opendaylight.org/gerrit/#/c/69325/\r
-\r
-2. Have you tested the latest release candidate? Yes - No issues found\r
-\r
-3. Do you have CSIT failures associated with the latest release candidate? No\r
-\r
- - Updated tracking spreadsheet for failures: Not Applicable\r
-\r
-4. Do you plan to address CLM violations applicable to your project\r
- post-release? No\r
-\r
- - CLM violations may be addressed if there's sufficient interest from the\r
- Packetcable community.\r
-\r
-5. Do you approve making the latest release candidate the official Opendaylight\r
- release? Yes\r
-\r
-6. Feedback on this release:\r
-\r
- - None\r
+++ /dev/null
-.. Instructions\r
-.. 1. Replace Project Name with your actual project name, ensure you have\r
-.. the same number of ='s as the length of your project in the line before\r
-.. and the line after.\r
-.. 2. Replace "xyz12" for item 1 with your actual gerrit patch number\r
-.. 3. Remove the (Yes/No) or (Yes/No/Not Applicable) answer at the end of\r
-.. each question with your actual response: Yes, No, Not Applicable\r
-.. 4. For detailed information on each item, use a sub list with a -\r
-.. in front that aligns with the text above and ensure you have a blank\r
-.. line before it.\r
-\r
-=========================\r
-Service Function Chaining\r
-=========================\r
-\r
-1. Gerrit patch for release notes of this major release:\r
-\r
- - https://git.opendaylight.org/gerrit/69324\r
-\r
-2. Have you tested the latest release candidate? Yes\r
-\r
- - No issues found\r
-\r
-3. Do you have CSIT failures associated with the latest release candidate? No\r
-\r
- - Updated tracking spreadsheet for failures: Not Applicable\r
-\r
-4. Do you plan to address CLM violations applicable to your project\r
- post-release? No\r
-\r
-5. Do you approve making the latest release candidate the official Opendaylight\r
- release? Yes\r
-\r
-6. Feedback on this release:\r
-\r
- - None\r
+++ /dev/null
-====\r
-snmp\r
-====\r
-\r
-1. Gerrit patch for release notes of this major release:\r
-\r
- - https://git.opendaylight.org/gerrit/#/c/69638\r
-\r
-2. Have you tested the latest release candidate? Yes\r
-\r
- - No issues found\r
-\r
-3. Do you have CSIT failures associated with the latest release candidate? No\r
-\r
-4. Do you plan to address CLM violations applicable to your project\r
- post-release? Yes\r
-\r
-5. Do you approve making the latest release candidate the official Opendaylight\r
- release? Yes\r
-\r
-6. Feedback on this release:\r
-\r
- - None\r
+++ /dev/null
-========\r
-SNMP4SDN\r
-========\r
-\r
-1. Gerrit patch for release notes of this major release:\r
-\r
- - https://git.opendaylight.org/gerrit/#/c/69303/\r
-\r
-2. Have you tested the latest release candidate? Yes\r
-\r
- - No issues found\r
-\r
-3. Do you have CSIT failures associated with the latest release candidate? NA (system test waiver)\r
-\r
-4. Do you plan to address CLM violations applicable to your project\r
- post-release? No\r
-\r
-5. Do you approve making the latest release candidate the official Opendaylight\r
- release? Yes\r
-\r
-6. Feedback on this release:\r
-\r
- - None\r
+++ /dev/null
-===\r
-SXP\r
-===\r
-\r
-1. Gerrit patch for release notes of this major release:\r
-\r
- - https://git.opendaylight.org/gerrit/#/c/69204/\r
-\r
-2. Have you tested the latest release candidate? Yes\r
-\r
- - SXP-127, SXP-128, SXP-129, SXP-131, SXP-133, SXP-135, SXP-137\r
-\r
-3. Do you have CSIT failures associated with the latest release candidate? Yes\r
-\r
- - Updated tracking spreadsheet for failures: Yes\r
-\r
-4. Do you plan to address CLM violations applicable to your project\r
- post-release? Not Applicable\r
-\r
-5. Do you approve making the latest release candidate the official Opendaylight\r
- release? Yes\r
-\r
-6. Feedback on this release:\r
-\r
- - None\r
+++ /dev/null
-===\r
-USC\r
-===\r
-\r
-1. Gerrit patch for release notes of this major release:\r
-\r
- - `USC Release Notes <https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/release-notes/projects/usc.rst;>`_\r
-\r
-2. Have you tested the latest release candidate? Yes\r
-\r
- - No issues found\r
-\r
-3. Do you have CSIT failures associated with the latest release candidate? No Blockers\r
-\r
- - Updated tracking spreadsheet for failures: Yes\r
-\r
-4. Do you plan to address CLM violations applicable to your project\r
- post-release? Yes\r
-\r
-5. Do you approve making the latest release candidate the official Opendaylight\r
- release? Yes\r
-\r
-6. Feedback on this release:\r
-\r
- - None\r
+++ /dev/null
-===\r
-vtn\r
-===\r
-\r
-1. Gerrit patch for release notes of this major release:\r
-\r
- - https://git.opendaylight.org/gerrit/#/c/69651/\r
-\r
-2. Have you tested the latest release candidate? yes\r
-\r
- - Manager Validated by CSIT\r
- - Tested Coordinator Offline\r
-\r
-3. Do you have CSIT failures associated with the latest release candidate? Yes\r
-\r
- - Updated tracking spreadsheet for failures: Yes\r
-\r
-4. Do you plan to address CLM violations applicable to your project\r
- post-release? Not Applicable\r
-\r
-5. Do you approve making the latest release candidate the official Opendaylight\r
- release? Yes\r
-\r
-6. Feedback on this release:\r
-\r
- - None\r
+++ /dev/null
-.. Instructions\r
-.. 1. Replace Project Name with your actual project name, ensure you have\r
-.. the same number of ='s as the length of your project in the line before\r
-.. and the line after.\r
-.. 2. Replace "xyz12" for item 1 with your actual gerrit patch number\r
-.. 3. Remove the (Yes/No) or (Yes/No/Not Applicable) answer at the end of\r
-.. each question with your actual response: Yes, No, Not Applicable\r
-.. 4. For detailed information on each item, use a sub list with a -\r
-.. in front that aligns with the text above and ensure you have a blank\r
-.. line before it.\r
-\r
-============\r
-Project Name\r
-============\r
-\r
-1. Gerrit patch for release notes of this major release:\r
-\r
- - https://git.opendaylight.org/gerrit/#/c/xyz12/\r
-\r
-2. Have you tested the latest release candidate? (Yes/No)\r
-\r
- - (If yes, list JIRA issues found or state "No issues found")\r
- - (If no, state rationale, e.g. "Tested by downstream projects")\r
-\r
-3. Do you have CSIT failures associated with the latest release candidate? (Yes/No)\r
-\r
- - Updated tracking spreadsheet for failures: (Yes/No/Not Applicable)\r
-\r
-4. Do you plan to address CLM violations applicable to your project\r
- post-release? (Yes/No/Not Applicable)\r
-\r
-5. Do you approve making the latest release candidate the official Opendaylight\r
- release? (Yes/No)\r
-\r
-6. Feedback on this release:\r
-\r
- - Feedback 1 (or None)\r
- - Feedback 2\r
- - Feedback 3\r
+++ /dev/null
-============
-Project Name
-============
-
-#. Have you tested your code in the release candidate? Yes/No
-
- - Provide a link to the release candidate you tested
- - If yes, did you find any issues?
- - If you found issues, do you believe any of them should block this release
- of OpenDaylight until they are resolved?
- - Please list all the issues and note if they are blocking
Code Review / docs.git / commitdiff