Topics

[release] Oxygen M1 Status Reminder

Kevin Kershaw <K.Kershaw@...>
 

Hello Kit & ODL teams.

 

My apologies for sending this late but here is the M1 Status readout for the Packetcable Project:

 

Best regards,

 

Kevin Kershaw

CableLabs

 

 

1. Project PTL:

   - Steve Pisarski

   - email: s.pisarski@...

   - IRC handle: N/A

   - I have reviewed the PTL Requirements - Yes

 

2. Project Contact:

   - Kevin Kershaw

   - email: k.kershaw@...

   - IRC handle: N/A

 

3. Test Contact:

   - Kevin Kershaw

   - k.kershaw@...

   - IRC handle - N/A

 

4. Documentation Contact

   - Kevin Kershaw

   - email: k.kershaw@...

   - IRC handle: N/A

 

5. Does your project have any updates on any previously-incomplete items from

   prior milestone readouts?

   - No.  No previously-incomplete items.

 

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 [2]_? No

 

8. Is your project release plan finalized?  Yes

   - Link to final release plan wiki page –

        https://wiki.opendaylight.org/view/PacketCablePCMM:Release_Plan_Oxygen

 

 

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?

   No special dependency requests for Packetcable Oxygen.

 

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

 

-------------------------------------------------

 

 

From: release-bounces@... [mailto:release-bounces@...] On Behalf Of Kit Lou
Sent: Thursday, October 26, 2017 6:37 AM
To: packetcable-dev@...

Cc: Release <release@...>
Subject: [release] Oxygen M1 Status Reminder

 

This is a friendly reminder for the projects below to complete their M1 milestone status readout as soon as possible (within a week) as it is past due:

aaa, coe, dlux, dluxapps, eman, faas, infrautils, mdsal, netvirt, nic, ocpplugin, odlparent, of-config, openflowplugin, opflex, packetcable, snmp, sxp, tsdr, unimgr, yangtools

 

As communicated earlier, milestone status needs to be submitted as reStructuredText file (similar to release notes) into the docs project - see Section 4, item aa in TSC meeting minutes [1].   All submitted and merged milestone readouts can be viewed here to make them readily accessible [2] - note that we have converted the M0 emails into rst files for all the participating projects.

 

Please make a copy of the m1 status template file [3], update, and submit your milestone readout into this folder of the docs project:  "docs/release-process/milestone-readouts/m1".

 

There is a useful online reStructuredText tool [4] you can use to validate your rst file contents - copy the rst file contents into the left pane and you will see the rendered HTML on the right pane.

 

Kit Lou <klou.external@...>
 

Hello Kevin & Packetcable Project Team,

Thanks for the email!  Could you please put the contents into a rst file (packetcable.rst) under docs/release-process/milestone-readouts/m1 and submit a gerrit patch?

If you have problems doing that, please let me know and I can do that for you.  

Best Regards,
Kit Lou

On Fri, Nov 3, 2017 at 1:10 PM, Kevin Kershaw <K.Kershaw@...> wrote:

Hello Kit & ODL teams.

 

My apologies for sending this late but here is the M1 Status readout for the Packetcable Project:

 

Best regards,

 

Kevin Kershaw

CableLabs

 

 

1. Project PTL:

   - Steve Pisarski

   - email: s.pisarski@...

   - IRC handle: N/A

   - I have reviewed the PTL Requirements - Yes

 

2. Project Contact:

   - Kevin Kershaw

   - email: k.kershaw@...

   - IRC handle: N/A

 

3. Test Contact:

   - Kevin Kershaw

   - k.kershaw@...

   - IRC handle - N/A

 

4. Documentation Contact

   - Kevin Kershaw

   - email: k.kershaw@...

   - IRC handle: N/A

 

5. Does your project have any updates on any previously-incomplete items from

   prior milestone readouts?

   - No.  No previously-incomplete items.

 

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 [2]_? No

 

8. Is your project release plan finalized?  Yes

   - Link to final release plan wiki page –

        https://wiki.opendaylight.org/view/PacketCablePCMM:Release_Plan_Oxygen

 

 

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?

   No special dependency requests for Packetcable Oxygen.

 

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

 

-------------------------------------------------

 

 

From: release-bounces@lists.opendaylight.org [mailto:release-bounces@lists.opendaylight.org] On Behalf Of Kit Lou
Sent: Thursday, October 26, 2017 6:37 AM
To: packetcable-dev@lists.opendaylight.org

Cc: Release <release@....org>
Subject: [release] Oxygen M1 Status Reminder

 

This is a friendly reminder for the projects below to complete their M1 milestone status readout as soon as possible (within a week) as it is past due:

aaa, coe, dlux, dluxapps, eman, faas, infrautils, mdsal, netvirt, nic, ocpplugin, odlparent, of-config, openflowplugin, opflex, packetcable, snmp, sxp, tsdr, unimgr, yangtools

 

As communicated earlier, milestone status needs to be submitted as reStructuredText file (similar to release notes) into the docs project - see Section 4, item aa in TSC meeting minutes [1].   All submitted and merged milestone readouts can be viewed here to make them readily accessible [2] - note that we have converted the M0 emails into rst files for all the participating projects.

 

Please make a copy of the m1 status template file [3], update, and submit your milestone readout into this folder of the docs project:  "docs/release-process/milestone-readouts/m1".

 

There is a useful online reStructuredText tool [4] you can use to validate your rst file contents - copy the rst file contents into the left pane and you will see the rendered HTML on the right pane.