Hi,
Okay, thanks for looking that up, I couldn’t find it.
The most obvious hook would be change-merged, although getting to the Bug: tag in the commit message could be a challenge.
Doing this stuff manually is just a pain, this is stuff that computers are simply way better at, so we have to figure a way to make them do it. But in the mean time, yes, developers which are merging changes, please check back at the bugs they address. And don’t worry if you forget, we’ll just have a bug squashing session at SharkFest EU to clean it up.
Thanks, Jaap
This was briefly discussed on -core back in March (when you brought it up then).
Copy/pasted the comments from there (conversation between you and Gerald):
>> It looks like we've run into j2bugzilla issue:
>>
>> https://github.com/TomRK1089/j2bugzilla/issues/14
>
> That is unfortunate, but ...
>
>>
>> It also looks like we're the only people on the planet trying to integrate Gerrit and Bugzilla.
>
> things like this makes this such a cool project to work on. :)
As an alternative to its-bugzilla we could ping and close bugs using hook scripts:
Anyone feel like writing (and debugging) a script?
I've been trying to keep up "manually" with closing bugs (especially if I'm the one giving the +2 and submitting) because I'm not a script writer, but until the issue is addressed, it would be appreciated if developers would close their bugs once patches with Bug: XXXX tagline are submitted.
___________________________________________________________________________ Sent via: Wireshark-dev mailing list < wireshark-dev@xxxxxxxxxxxxx> Archives: https://www.wireshark.org/lists/wireshark-devUnsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
|
