On Thu, Oct 19, 2017 at 3:05 PM, Jamo Luhrsen <jluhr...@gmail.com> wrote:

> I asked in Jira for them to provide a link to their patch. If they have a
> patch
> and it's ok to merge after controller committers review it, we can just
> resolve
> the bug and it will be there for nitro SR1.
>
> if no patch comes, I think the evidence so far suggests we can downgrade
> it from
> blocker and release SR1 without a fix.
>
>
>
I already downgraded it to Medium in JIRA. The question is why did An all
of a sudden elevate it to Blocker (and after the switch-over) with no
reason... As I said, seems like a mistake somehow. In any event if the
creator pushes their patch soon we can merge it but they said they were
going to push it over a month ago :)


> JamO
>
>
> On 10/19/2017 11:49 AM, Tom Pantelis wrote:
> >
> > On Thu, Oct 19, 2017 at 2:45 PM, Ryan Goulding <ryandgould...@gmail.com
> <mailto:ryandgould...@gmail.com>> wrote:
> >
> >     If I'm not mistaken, from the history it would appear An Ho was the
> one to escalate the severity to "Blocker" in Bugzilla
> >     [0].  An can you comment on this to clarify why it was elevated?
> >
> >
> > yeah and it was done yesterday after the switch-over I think. Seems odd
> - seems like a mistake.
> >
> >
> >
> >     Thanks!
> >
> >     Regards,
> >
> >     Ryan Goulding
> >
> >     [0] https://bugs.opendaylight.org/show_activity.cgi?id=9163 <
> https://bugs.opendaylight.org/show_activity.cgi?id=9163>
> >
> >     On Thu, Oct 19, 2017 at 2:39 PM, Tom Pantelis <tompante...@gmail.com
> <mailto:tompante...@gmail.com>> wrote:
> >
> >
> >         On Thu, Oct 19, 2017 at 2:29 PM, Kit Lou <
> klou.exter...@gmail.com <mailto:klou.exter...@gmail.com>> wrote:
> >
> >             Good question Tom!  Thanks for your feedback!  What is the
> likelihood of someone encountering the issue?  Is
> >             there a workaround?
> >
> >             This issue was just elevated to "Blocker" yesterday in
> between the JIRA migration.  It was at "Normal" severity
> >             in JIRA and "Blocker" in bugzilla.  I had to manually adjust
> the severity in JIRA to match bugzilla this morning.
> >
> >
> >         I don't recall it ever being a blocker in bugzilla - it wasn't a
> couple days ago when I last looked at the clustering
> >         bugs (there haven't been any blockers in a while). I don't know
> how it all of a sudden got elevated to "Blocker". If
> >         you want it to be a blocker then that's fine but, as I
> mentioned, it's an edge case and has been there all along. The
> >         person that created it a while ago stated they had a patch but
> never pushed it.
> >
> >
> >
> >             TSC Members,
> >
> >             Should we hold nitrogen SR1 for this issue?
> >
> >             Best Regards,
> >             Kit
> >
> >
> >             On Thu, Oct 19, 2017 at 1:18 PM, Tom Pantelis <
> tompante...@gmail.com <mailto:tompante...@gmail.com>> wrote:
> >
> >
> >
> >                 On Thu, Oct 19, 2017 at 2:01 PM, Kit Lou <
> klou.exter...@gmail.com <mailto:klou.exter...@gmail.com>> wrote:
> >
> >                     Hi Controller Team,
> >
> >                     This email is to inform you that there is a blocker
> bug CONTROLLER-1770 in JIRA [1] against the
> >                     controller project blocking the upcoming nitrogen
> SR1 release.
> >
> >                     Please be ready to help with resolving the issue.
> Thanks!
> >
> >
> >                 Why is this a blocker for SR1 when it wasn't a blocker
> for nitrogen?  Plus this is an edge case that has been
> >                 there all along.
> >
> >
> >
> >                     Best Regards,
> >                     Kit Lou
> >
> >                     [1] https://jira.opendaylight.org/
> browse/CONTROLLER-1770 <https://jira.opendaylight.
> org/browse/CONTROLLER-1770>
> >
> >
> >                     _______________________________________________
> >                     release mailing list
> >                     rele...@lists.opendaylight.org <mailto:
> rele...@lists.opendaylight.org>
> >                     https://lists.opendaylight.
> org/mailman/listinfo/release
> >                     <https://lists.opendaylight.
> org/mailman/listinfo/release>
> >
> >
> >
> >
> >
> >         _______________________________________________
> >         TSC mailing list
> >         t...@lists.opendaylight.org <mailto:t...@lists.opendaylight.org>
> >         https://lists.opendaylight.org/mailman/listinfo/tsc <
> https://lists.opendaylight.org/mailman/listinfo/tsc>
> >
> >
> >
> >
> >
> > _______________________________________________
> > controller-dev mailing list
> > controller-dev@lists.opendaylight.org
> > https://lists.opendaylight.org/mailman/listinfo/controller-dev
> >
>
_______________________________________________
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev

Reply via email to