Guys,
        In an attempt to get some discussion going between projects on release plans, I have been reading through the
release plans for each project and trying to get a sense of where there are things that projects probably should talk about timing wise.

        This is the first of the email from that reading, in the hope of sparking conversation.

        Looking at the openflowplugin release plan:
https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:Helium_Release_Plan#Release_Milestones
        and the controller release plan:
https://wiki.opendaylight.org/view/OpenDaylight_Controller:Helium_Release_Plan#Release_Milestones
        both are listing a goal of switching over to the openflowplugin as the default openflowplugin at M2 (6/9/14).
        There are adapters so that existing flow programming should continue to work correctly, and
https://jenkins.opendaylight.org/integration/job/integration-csit-base-of13/
        is currently running 116 (and rapidly growing, 14 new tests yesterday) integration tests successfully.
        Since VTN and ovsdb are doing flow programming, I wanted to make sure that VTN, openflowplugin, and openflowjava
were talking so that we can work together towards these.  Things that it occurs to me might be a good idea would include
getting the the vtn and ovsdb integration tests running on the openflowplugin, so that we can shake out any bugs and get them
fixed for the M2 cutover.

        Also, if there are things that ovsdb/vtn (or other flow programming projects) need from openflowplugin/openflowjava, we should
get those called out, figure out who is going to work on them, and get them into the openflowplugin/java release plans.

Ed


_______________________________________________
openflowjava-dev mailing list
openflowjava-dev@...
https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev