On Wed, Aug 17, 2016 at 1:45 PM, Eyal Edri <firstname.lastname@example.org> wrote:
> I still thinks its a very valuable hook and we are aware of the fact it has
> bugs, especially with patches on master branch and 4.0.
> Shlomi from the infra team is working on a solution for it as we speak and
> we hope to have a solution in the next few days, however it's not trival to
> test and requires setting up a staging env and improve loga for the hooks
How do you plan to solve this?
Only the owner of the bug knows if the all the required patches are merged
and backported to the correct repositories.
> On Aug 17, 2016 12:06 PM, "Eli Mesika" <email@example.com> wrote:
>> I also got this, especially when bugs should be back-ported
>> +1 for option #1
>> On Wed, Aug 17, 2016 at 10:10 AM, Yedidyah Bar David <firstname.lastname@example.org>
>>> Hi all,
>>> We currently have a bot that automatically moves bugs from POST to
>>> if all linked patches on gerrit are merged.
>>> It happened to me personally several times that this was a wrong thing to
>>> either because a new patch was still needed but not pushed yet, or
>>> an existing patch should have been back-ported to another branch and
>>> yet. Since I usually pay more attention to my bug in POST, I sometimes
>>> this and handled the missing patches (backports, usually) later than I
>>> if left on POST.
>>> I have a feeling I am not the only one. So I suggest to stop doing this.
>>> I can think of several alternatives:
>>> 1. Do nothing. I think that's reasonable - I think most people pay more
>>> attention to POST bugs anyway.
>>> 2. Set needinfo on bug owner.
>>> 3. Send some alert email to relevant people (bug owner, existing patches
>>> perhaps others - e.g. reviewers of existing patches, perhaps those
>>> that actually reviewed, etc.). Need to think how to make it not too
>>> annoying for others but
>>> still effective also if owner is on long PTO or something like that. New
>>> doesn't have to be very specific - can be called something like
>>> needed' or something like that.
>>> 4. Add a new flag for that and set it. This will allow easier
>>> What do you think?
>>> Devel mailing list
>> Devel mailing list
> Devel mailing list