Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index


https://bugs.freedesktop.org/show_bug.cgi?id=53092

--- Comment #10 from Lionel Elie Mamane <lionel@mamane.lu> ---
(In reply to comment #4)
Please remember that some of us are put into cc for some hundred bugs by the
qa team. (...) if there are now even more mails that are totally useless
for us we will miss important bugzilla mails.

A developer who would be the target audience for comment notification in
gerrit has other ways to get this information than to use bugzilla.

IMHO a single notification of "a patch for this bug has been submitted to
branch X" (so one comment per gerrit change and per release (not feature)
branch) would be relevant to the CCed developers. Else, they get exactly zero
notification about it, unless the patch uploader specifically adds these
developers as reviewers on the gerrit side.

Actually, I kinda would appreciate an optional "automatically make me a
reviewer on each gerrit change that is related to a bug where I'm CC" feature.

Some more information about the git bugzilla script. The intention of it was
mainly to report to the reporter and the QA guys when a fix will be included
into a release branch and help them test the fix without checking back which
build will contain the fix.

For the QA guys, which I presume can be expected to know about our procedures,
then we don't even need a comment, the whiteboard keyword is enough.

For the reporter, OK, he might not understand "target:x.y.z", the comment is
more user-friendly.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.