An,
I just cherry-picked the change to stable/boron [0]
The SFC testing contact, Miguel Angel Muñoz Gonzalez, has verified that
the change does not introduce any regressions, and that dependent
project will not be adversely affected.
Regards,
Brady
[0] https://git.opendaylight.org/gerrit/#/c/45264/
On 06/09/16 19:52, An Ho wrote:
If the bug is a blocking issue, I’m fine with fixing it in RC3 since
we will be respinning a new build and a patch is already available. If
the patch has been tested/confirmed that it does not adversely affect
dependent projects and does not introduce any new regression on
functionality, please cherry pick to the stable/boron branch and
provide the patch ID.
Once you provide a patch ID for stable/boron (not master), I will
update the tracking spreadsheet accordingly.
Best Regards,
An Ho
*From:*Brady Allen Johnson [mailto:[email protected]]
*Sent:* Tuesday, September 06, 2016 10:45 AM
*To:* An Ho; Robert Varga; [email protected]
*Subject:* Re: Bug 6648 - Not possible to add additional Service
Function's dataplane locators
An,
We discovered the root cause of this problem today, with the help of
Robert, while investigating a failing Boron SFC Integration test.
Originally I wanted to fix this bug in Boron RC3 and marked the bug as
so, but after talking to Jamo, he said it would be ok to fix in Boron
SR1 without causing the SFC features to be marked experimental as long
as we link the test failure to the bug.
The fix is very simple, and the patch [0] has already been merged in
Carbon/master. Considering SFC has a blocker bug fix coming tomorrow
morning GMT+1, I could cherry-pick this [0] to stable/boron if you're
ok with that. Otherwise the test will still fail, but be linked to a
bug until Boron SR1.
Regards,
Brady
[0] https://git.opendaylight.org/gerrit/#/c/45233/
<https://git.opendaylight.org/gerrit/#/c/45233/>
On 06/09/16 19:25, An Ho wrote:
Hi Robert, Brady,
During the MDSAL call, some concerns were raised as to whether Bug
6648 is a blocking issue in the Boron release. However, the
bugzilla note for the bug indicates it a “normal” with a target of
“Boron-SR1” in October. Could we get some clarity on the priority
and target for this bug. Is it a true blocker that must be fixed
before Boron is released?
Best Regards,
An Ho
_______________________________________________
sfc-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/sfc-dev
