Let's wait for Jozef & team to work on these fixes. As you guys also said
over IRC its better that we get this done right.

Jozef - if we need all three patches - please let us know and also please
fix all the merge conflicts. Also please have +1 on the other patches (if
there are other folks who can review it in your day time).

On Thu, May 5, 2016 at 11:47 AM, Luis Gomez <ece...@gmail.com> wrote:

> There is a merge conflict when trying automatic cherry-pick, so the patch
> may need the other 2 or part of them.
>
>
> > On May 5, 2016, at 11:36 AM, Jamo Luhrsen <jluhr...@gmail.com> wrote:
> >
> > can we rebase and merge (just 38369) and get a respin and let the tests
> > run, just as a head start; in case the answer from Joezf is that we don't
> > need the other patches?
> >
> > JamO
> >
> > On 05/05/2016 11:33 AM, Abhijit Kumbhare wrote:
> >> In that case - may be better to wait till tomorrow for Jozef to respond
> whether the other two are needed (& safe) - since Luis only tested
> >> with https://git.opendaylight.org/gerrit/#/c/38369/ (and found that it
> worked).
> >>
> >> On Thu, May 5, 2016 at 11:24 AM, Thanh Ha <thanh...@linuxfoundation.org
> <mailto:thanh...@linuxfoundation.org>> wrote:
> >>
> >>    Looks like that patch depends on 2 patches that need to be merged
> before:
> >>
> >>    https://git.opendaylight.org/gerrit/#/c/38111/15
> >>    https://git.opendaylight.org/gerrit/#/c/37661/19
> >>
> >>    Do we need them? if so then please +2 those patches too. If not then
> patch 38369 needs to be rebased so that it doesn't depend on other
> >>    unsubmitted patches.
> >>
> >>    Regards,
> >>    Thanh
> >>
> >>
> >>
> >>    On 5 May 2016 at 14:17, Abhijit Kumbhare <abhijitk...@gmail.com
> <mailto:abhijitk...@gmail.com>> wrote:
> >>
> >>        Since the TSC decision is to respin, I have +2'ed
> https://git.opendaylight.org/gerrit/#/c/38369/ - but the branch is locked.
> >>
> >>        Thanh - can you please merge it?
> >>
> >>        On Thu, May 5, 2016 at 6:03 AM, Colin Dixon <
> co...@colindixon.com <mailto:co...@colindixon.com>> wrote:
> >>
> >>            Noted. I'll bring this up on the TSC call today. Is it
> possible to have somebody who deeply understands the bug and it's
> consequences
> >>            attend the meeting?
> >>
> >>            Also, have we established if we know of any external
> consumers of the Lithium plugin-in in Beryllium?
> >>
> >>            --Colin
> >>
> >>
> >>            On Wed, May 4, 2016 at 6:33 PM, An Ho <an...@huawei.com
> <mailto:an...@huawei.com>> wrote:
> >>
> >>                Hi Colin,
> >>
> >>                Our latest build [1] has a critical blocker bug in
> OPENFLOWPLUGIN [2] related to the OpenFlow Li Plugin Cluster test
> failures.  This
> >>                is a regression that may affect end users who run the
> controller with the new OpenFlow Li Plugin in Beryllium.  A patch [3] has
> been
> >>                created to fix the issues and is currently awaiting
> review.  More details can be found on the status page [4].  We have two
> options:
> >>
> >>                Option #1: After the patch is merged, we schedule a
> respin of the build to incorporate the patches fixing the OPENFLOWPLUGIN
> critical
> >>                bug, then have projects sign off on the newly respun
> build.  This may have the potential of further delay of the release of
> Beryllium SR2.
> >>                Option #2: Release Beryllium SR2 with the known
> OPENFLOWPLUGIN regression.
> >>
> >>                Best Regards,
> >>                An Ho
> >>
> >>                [1]
> https://wiki.opendaylight.org/view/Simultaneous_Release:Beryllium_Release_Plan#Beryllium_SR2_Download
> >>                [2] https://bugs.opendaylight.org/show_bug.cgi?id=5523
> >>                [3] https://git.opendaylight.org/gerrit/#/c/38369/
> >>                [4]
> https://wiki.opendaylight.org/view/Simultaneous_Release/Beryllium/SR2/Status
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>        _______________________________________________
> >>        release mailing list
> >>        rele...@lists.opendaylight.org <mailto:
> rele...@lists.opendaylight.org>
> >>        https://lists.opendaylight.org/mailman/listinfo/release
> >>
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> TSC mailing list
> >> t...@lists.opendaylight.org
> >> https://lists.opendaylight.org/mailman/listinfo/tsc
> >>
> > _______________________________________________
> > TSC mailing list
> > t...@lists.opendaylight.org
> > https://lists.opendaylight.org/mailman/listinfo/tsc
>
>
_______________________________________________
openflowplugin-dev mailing list
openflowplugin-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev

Reply via email to