Table Type Patterns (ttp)

0. Please provide updates on any previously-incomplete items from prior milestone readouts. n/a
1. Have you completed the project checklist? Yes
     (link to a merged patch in gerrit): https://git.opendaylight.org/gerrit/#/c/24211/
     (link to a mail from your mailing list): https://lists.opendaylight.org/pipermail/ttp-dev/2015-August/000095.html
     (link to a bug for your project; you can create a dummy one and close it if need be): https://bugs.opendaylight.org/show_bug.cgi?id=1881
     (link to an artifact published from your project in nexus): https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/ttp/parser/0.2.0-SNAPSHOT/
     (link to a sonar report): https://sonar.opendaylight.org/dashboard/index/20096
     (link to your root pom file): https://git.opendaylight.org/gerrit/gitweb?p=ttp.git;a=blob;f=pom.xml;hb=HEAD
2. Does your project have any special needs in CI Infrastructure (tools or configuration)? No
3. Is your project release plan finalized? Yes
     https://wiki.opendaylight.org/view/Table_Type_Patterns/Beryllium/Release_Plan
     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, when they exist
         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, when they exist
4. All project dependencies (requests on other project's release plans) have been acknowledged and documented by upstream projects?
     The ttp project has possible (new) dependencies on openflowplugin, openflowjava, and didm in Beryllium. We have sent e-mail to that effect.
     As an aside, ttp depends on the JSON codecs (in a combination of yantools and netconf?) for binding aware data types in non-standard ways.
5. Were there any project-specific deliverables planned for this milestone? No


Action items:
* Curt to send M2 status report (above) to release
* Curt to send e-mail to openflowplugin-dev, openflowjava-dev, didm-dev, release saying we might depended on them
    * Follow-up e-mail to DIDM either kicking off planning via e-mail or setting up a meeting.
    * _If_ we started to think about implementing TTP negotiation, we might want to interact with OpenFlow Plugin/Java in a more bidirectional way.
* Colin to figure out what subset of yangtools, controller and/or netconf we depend on in weird ways.
    * Either Colin or Curt to send e-mail to them saying so.