l2switch M3 readout
[docs.git] / docs / release-process / milestone-readouts / m3 / netconf.rst
1
2 =======
3 Netconf
4 =======
5
6 1. Do you have any previously-incomplete items from prior milestone
7    readouts? No
8
9 2. Has your project achieved API freeze such that all externally accessible
10    Stable or Provisional APIs will not be modified after now? Yes
11
12 3. Do you have content in your project documentation? Yes
13
14    - http://docs.opendaylight.org/en/stable-nitrogen/release-notes/projects/netconf.html#documentation
15
16 4. Has your project met the requirements to be included in Maven Central [2]_?
17    Yes
18
19 5. Were project-specific deliverables planned for this milestone delivered
20    successfully? No Deliverables
21
22 6. Have you started automated system testing for your top-level features? Yes
23
24    - https://jenkins.opendaylight.org/releng/view/netconf/
25
26 7. Does your project use any ports, including for testing? Yes
27
28    - http://docs.opendaylight.org/en/stable-nitrogen/release-notes/projects/netconf.html#security-considerations
29    - (If yes, have you updated the wiki [3]_ with all ports used? No) Netconf call-home TCP port 6666 is missing
30
31 8. Does your project build successfully in Autorelease? Yes
32
33    - https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-validate-autorelease-oxygen/226/
34
35 .. [1] Provide a link to a gerrit search for patches modifying the files
36        defined as specifying the API. For example:
37        https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
38 .. [2] http://central.sonatype.org/pages/requirements.html
39 .. [3] https://wiki.opendaylight.org/view/Ports
40 .. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements