ODL Parent
==========
-1. Project PTL:
+1. Project PTL: Stephen Kitt, skitt@redhat.com, skitt
- - Stephen Kitt
- - skitt@redhat.com
- - skitt
- - I have reviewed the PTL Requirements
+ - Yes, I have reviewed the PTL Requirements.
-2. Project Contact:
+2. Project Contact: Stephen Kitt, skitt@redhat.com, skitt
- - Stephen Kitt
- - skitt@redhat.com
- - skitt
+3. Test 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
+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
+ prior milestone readouts? No
6. Were project-specific deliverables planned for this milestone delivered
- successfully?
-
- - No deliverables
+ successfully? No deliverables
-7. Does your project have any special needs in CI Infrastructure?
+7. Does your project have any special needs in CI Infrastructure? No
- - No
+8. Is your project release plan finalized? Yes
-8. Is your project release plan finalized?
-
- - Yes: https://wiki.opendaylight.org/view/ODL_Parent:Oxygen_Release_Plan
+ - `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? N/A
+ - 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? They will be by M2
+ each API? *Yes*
- Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? Yes
+ for each API? *Yes*
10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? N/A
-
- - No project dependencies
+ been acknowledged and documented by upstream projects? Not Applicable
-11. Will your project have top-level features not requiring system test?
-
- - Yes, ODL parent usually gets an automatic waiver
+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, see above
+ top-level features requiring system test? No
OF-CONFIG
=========
-1. Project PTL:
+1. Project PTL: Wei Meng, meng.wei2@zte.com.cn, valley
- - Wei Meng
- - meng.wei2@zte.com.cn
- - valley
- Yes, I have reviewed the PTL Requirements
-2. Project Contact:
+2. Project Contact: Wei Meng, meng.wei2@zte.com.cn, valley
- - Wei Meng
- - meng.wei2@zte.com.cn
- - valley
+3. Test 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
+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? (Yes/No)
-
- - No
+ prior milestone readouts? No
6. Were project-specific deliverables planned for this milestone delivered
- successfully? (No Deliverables/Yes/No)
+ successfully? No Deliverables
- - No Deliverables
+7. Does your project have any special needs in CI Infrastructure? No
-7. Does your project have any special needs in CI Infrastructure? (Yes/No)
+8. Is your project release plan finalized? Yes
- - No
+ - `Release plan <https://wiki.opendaylight.org/view/OF-CONFIG:Oxygen:Release_Plan>`_
-8. Is your project release plan finalized? (Yes/No)
+9. Do you have all APIs intended to be externally consumable listed?
- - 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? (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
+ - 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
+ each API? *Yes*
- Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? Yes
+ for each API? *Yes*
10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? (Yes/No)
+ been acknowledged and documented by upstream projects? Yes
- - Yes. controller, mdsal, NETCONF, YANGTOOL, dlux, odlparent
+ - controller
+ - mdsal
+ - NETCONF
+ - YANGTOOL
+ - dlux
+ - odlparent
-11. Will your project have top-level features not requiring system test?
- (Yes/No)
-
- - No
+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/No)
-
- - Yes
+ top-level features requiring system test? Yes
OpenFlow Plugin
===============
-1. Project PTL:
+1. Project PTL: Abhijit Kumbhare, abhijitkoss@gmail.com, abhijitkumbhare
- - Abhijit Kumbhare
- - abhijitkoss@gmail.com
- - abhijitkumbhare
- - I have reviewed the PTL Requirements [1]_
+ - Yes, I have reviewed the PTL Requirements [1]_.
-2. Project Contact:
+2. Project Contact: Abhijit Kumbhare, abhijitkoss@gmail.com, abhijitkumbhare
- - Abhijit Kumbhare
- - abhijitkoss@gmail.com
- - abhijitkumbhare
+3. Test Contact: Luis Gomez, ecelgp@gmail.com, LuisGomez
-3. Test Contact:
-
- - Luis Gomez
- - ecelgp@gmail.com
- - LuisGomez
-
-4. Documentation Contact
-
- - Shuva Jyoti Kar
- - shuva.jyoti.kar.87@gmail.com
- - shuva
+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
+ prior milestone readouts? No
6. Were project-specific deliverables planned for this milestone delivered
- successfully?
-
- - Yes
+ successfully? Yes
-7. Does your project have any special needs in CI Infrastructure [2]_?
+7. Does your project have any special needs in CI Infrastructure [2]_? No
- - No
+8. Is your project release plan finalized? Yes
-8. Is your project release plan finalized?
+ - `Release plan <https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:Oxygen_Release_Plan>`_
- Yes - (subject to reasonable changes)
- Link to final release plan wiki page: https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:Oxygen_Release_Plan
+9. Do you have all APIs intended to be externally consumable listed? Yes
-9. Do you have all APIs intended to be externally consumable listed? Yes - no change
-
- - Does each API have a useful short name? Yes - no change
- - Are the Java interface and/or YANG files listed for each API? Yes - no change
+ - 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 - no change
+ each API? Yes
- Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? Yes - no change
+ for each API? Yes
10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects?
-
- Yes. Depends on some offset 0 projects like ODL parent, controller, MD-SAL, etc. These have been acknowledged previous releases - no new dependencies & hence do not need to be acknowledged.
+ been acknowledged and documented by upstream projects? Yes
-11. Will your project have top-level features not requiring system test?
-
- - No
+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
+ top-level features requiring system test? Yes
**FOR NEW PROJECTS ONLY**
OpFlex
======
-1. Project PTL:
+1. Project PTL: Rob Adams, readams@readams.net, readams
- - Rob Adams
- - readams@readams.net
- - readams
- - I have reviewed the PTL Requirements
+ - Yes, I have reviewed the PTL Requirements.
-2. Project Contact:
+2. Project Contact: Rob Adams, readams@readams.net, readams
- - Rob Adams
- - readams@readams.net
- - readams
+3. Test 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
+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
+ prior milestone readouts? No
6. Were project-specific deliverables planned for this milestone delivered
- successfully?
-
- - No deliverables
+ successfully? No deliverables
-7. Does your project have any special needs in CI Infrastructure ? (Yes/No)
+7. Does your project have any special needs in CI Infrastructure ? No
- - No
+8. Is your project release plan finalized? No
-8. Is your project release plan finalized? (Yes/No)
+9. Do you have all APIs intended to be externally consumable listed?
- - No - I seem to have lost the ability to edit the wiki. This will
- be a very minor release with incremental changes and/or bug fixes.
-
-9. Do you have all APIs intended to be externally consumable listed? (Yes/No/Not Applicable)
-
- - Does each API have a useful short name? NA
- - Are the Java interface and/or YANG files listed for each API? NA
+ - 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? NA
+ each API? *Not Applicable*
- Do you call out the OSGi bundles and/or Karaf features providing the API
- for each API? NA
+ for each API? *Not Applicable*
10. Have all project dependencies requests on other projects' release plans
- been acknowledged and documented by upstream projects? (Yes/No)
-
- - None
+ been acknowledged and documented by upstream projects? Yes
-11. Will your project have top-level features not requiring system test?
- (Yes/No)
-
- - NA
+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/No)
-
- - We have no top-level Karaf features, but the code is unit tested
- in ODL infra and integration tested in our automated lab
- infrastructure for integration with Kubernetes, OpenStack and ACI.
+ top-level features requiring system test? Yes
OVSDB
=====
-1. Project PTL:
+1. Project PTL: Anil Kumar Vishnoi, vishnoianil@gmail.com, vishnoianil
- - Anil Kumar Vishnoi
- - vishnoianil@gmail.com
- - vishnoianil
- - Yes, I have reviewed the PTL Requirements [1]_
+ - Yes, I have reviewed the PTL Requirements [1]_.
-2. Project Contact:
+2. Project Contact: Anil Kumar Vishnoi, vishnoianil@gmail.com, vishnoianil
- - Anil Kumar Vishnoi
- - vishnoianil@gmail.com
- - vishnoianil
+3. Test Contact: Jamo Luhrsen, jluhrsen@redhat.com, jamoluhrsen
-3. Test Contact:
-
- - Jamo Luhrsen
- - jluhrsen@redhat.com
- - jamoluhrsen
-
-4. Documentation Contact
-
- - Anil Kumar Vishnoi
- - vishnoianil@gmail.com
- - vishnoianil
+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
+ prior milestone readouts? No
6. Were project-specific deliverables planned for this milestone delivered
- successfully?
-
- - No Deliverables
+ successfully? No Deliverables
-7. Does your project have any special needs in CI Infrastructure [2]_?
+7. Does your project have any special needs in CI Infrastructure [2]_? No
- - No
+8. Is your project release plan finalized? Yes
-8. Is your project release plan finalized?
-
- - Yes, available here: `Release plan <https://wiki.opendaylight.org/view/OpenDaylight_OVSDB:Oxygen_Release_Plan>`_
+ - `Release plan <https://wiki.opendaylight.org/view/OpenDaylight_OVSDB:Oxygen_Release_Plan>`_
9. Do you have all APIs intended to be externally consumable listed?
- yangtools, Implicit acknowledgement
-11. Will your project have top-level features not requiring system test?
-
- - No
+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
+ 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
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
-
Code Review / docs.git / commitdiff