On 4/19/18 10:46 AM, Luis Gomez wrote:
On Apr 19, 2018, at 7:16 AM, Tom Pantelis <[email protected]
<mailto:[email protected]>> wrote:
On Thu, Apr 19, 2018 at 9:14 AM, Vishal Thapar <[email protected]
<mailto:[email protected]>> wrote:
Hi Robert,
Could you please take a look at tell what I need to fix this breakage? I am
still not sure why is such a basic
code breaking like this.
Perhaps we should just revert the mdsal patch until this can get sorted out downstream - maybe discuss on the TSC call
today .
+1, without knowing the technical details of the change, I think we are missing something fundamental in the
upstream-downstream communication: in general for any valid change coming from upstream breaking downstream we need a
weather report including explanation why the change is required and some pointers on how to fix the potential failures.
This gives a chance for downstream projects to evaluate and accept the change as well as to prepare the required patches
to minimize the impact. If the breakage was unintentional or unexpected (no weather fired), I think the right thing to
do is to revert and start over writing the weather report.
in jira format, not on the wiki:
https://jira.opendaylight.org/browse/TSC-4
JamO
Regards,
Vishal.
_______________________________________________
mdsal-dev mailing list
[email protected] <mailto:[email protected]>
https://lists.opendaylight.org/mailman/listinfo/mdsal-dev
_______________________________________________
openflowplugin-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
_______________________________________________
openflowplugin-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
