Thanks Sai.

From: Sai MarapaReddy [mailto:[email protected]]
Sent: Friday, December 09, 2016 11:34 PM
To: Luis Gomez
Cc: Shuva Jyoti Kar; An Ho; [email protected]; 
[email protected]
Subject: Re: [L2switch-dev] [openflowplugin-dev] openflowplugin blocker bug

Shuva / Luis,

Thanks,

Please target it for Boron SR3.

On Thu, Dec 8, 2016 at 11:05 AM, Luis Gomez 
<[email protected]<mailto:[email protected]>> wrote:
Just remind this issue is not really critical but it is set as blocker because 
there is a change of behavior (small regression) from Beryllium to Boron. From 
this perspective I think it is OK to defer the fix for this to SR3 if both 
projects agree on that.

BR/Luis

On Dec 8, 2016, at 10:18 AM, Shuva Jyoti Kar 
<[email protected]<mailto:[email protected]>> wrote:

Sai,

Can we target this for Boron SR3 ?

Thanks
Shuva


From: 
[email protected]<mailto:[email protected]>
 [mailto:[email protected]] On Behalf Of Sai 
MarapaReddy
Sent: Friday, December 02, 2016 2:33 AM
To: An Ho
Cc: 
[email protected]<mailto:[email protected]>;
 
[email protected]<mailto:[email protected]>
Subject: Re: [openflowplugin-dev] openflowplugin blocker bug

Hi An,

I didn't get time to work on the bug. I request to carry forward it to SR3.

On Thu, Dec 1, 2016 at 9:49 AM, An Ho 
<[email protected]<mailto:[email protected]>> wrote:
Hi L2SWITCH and OPENFLOWPLUGIN Team,

We would like to kindly request an update on this OPENFLOWPLUGIN/L2SWITCH Boron 
Blocker Bug?  Please let us know the ETA for a fix or if we should retarget the 
blocker bug for Boron-SR3 instead.

Bug 6575 - l2switch does not work well when mininet is disconnected and 
connected with no time in-between

Best Regards,
An Ho

_______________________________________________
L2switch-dev mailing list
[email protected]<mailto:[email protected]>
https://lists.opendaylight.org/mailman/listinfo/l2switch-dev


_______________________________________________
openflowplugin-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev

Reply via email to