Hi Ryan Goulding, Many thanks for the correction. AAA has completed M3 milestone requirements.
Best Regards, An Ho From: Ryan Goulding [mailto:ryandgould...@gmail.com] Sent: Wednesday, February 01, 2017 5:07 PM To: Katie Zhang Cc: Marapareddy Sai; Christine; An Ho; aaa-...@lists.opendaylight.org; l2switch-dev@lists.opendaylight.org; snmp-...@lists.opendaylight.org; snmp4sdn-...@lists.opendaylight.org; usc-...@lists.opendaylight.org Subject: Re: Your Project is still missing M3 status No, AAA M3 status was sent January 17th, 2017 [0]. Hope this helps! Regards, Ryan Goulding [0] https://lists.opendaylight.org/pipermail/release/2017-January/009091.html On Wed, Feb 1, 2017 at 7:59 PM, Katie Zhang <katie.zhang.hua...@gmail.com<mailto:katie.zhang.hua...@gmail.com>> wrote: Hi Dear PTLs of : AAA, l2switch, snmp, snmp4sdn, USC This is a friendly remainder that your projects are still missing the M3 status. Please send your M3 status to release email list. thanks a lot. katie <Project Name> Functionality Freeze: 1. Final list of externally consumable APIs defined: Yes/No ** If you had any 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 haven't been delivered and the project you were expecting to receive them from. ** Note that you can only reasonably hold a project to something if you formally asked for it during the release planning process and they acknowledged that ask saying they would do it. 3. Were there any project-specific deliverables planned for this milestone? Yes/No ** If so, were they delivered? Yes/No Karaf Features Defined: 4. Are all your project's features that are intended for release added to the features.xml and checked into the integration git repository? Yes/No ** (please provide link to features.xml) ** (please provide link to the gerrit patch that checks into the integration git repository) 5. List all top-level, user-facing, and stable Karaf features for your project. ** For top-level, user-facing, and stable Karaf features, please provide a one-sentence description which a developer and/or user would find helpful. Documentation: 6. 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. ** Optional tutorials and how tos. 7. Have you checked in the AsciiDoc outlines to the docs repository? Yes/No ** (link to gerrit patch) Integration and Test: 8. Have you started automated system testing for your top-level features. Yes/No ** If yes, link to test report ** If no, why? 9. Have you filled out basic system test plan template [1] 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? Project Specific: 10. Have you updated your project facts with the project type category? Yes/No 11. Do you acknowledge the changes to the RC Blocking Bug Policy for Carbon Release [2]? Yes/No [0] https://wiki.opendaylight.org/view/Simultaneous_Release:Carbon_Release_Plan [1] https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template [2] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html -- Best katie
_______________________________________________ L2switch-dev mailing list L2switch-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/l2switch-dev
