[Mageia-bugsquad] Differentiate mails concerning update candidates and backports candidates (and ideally mga1/2)
stormi at laposte.net
Thu Jul 5 22:34:53 CEST 2012
Here at QA the bugzilla notifications we get at qa-bugs at ml.mageia.org are one
of our main tool to get information about what's going on regarding update
candidates. Every bit of information we can gather using one single look is a
gain in time and clarity.
Now that we will get backports to test, we would like to be able to
differentiate mails concerning updates from those concerning backports, ideally
with ability to filter in our mail client.
We envisioned 2 different solutions at tonights QA meeting, but maybe you have
*** Solution 1 : a qa-backports mailing list ***
Bug reports for backport validation would have to be assigned to qa-backports
instead of qa-bugs.
*** Solution 2 : formatted bug summary ***
We would keep only one mailing list, but mail subjects would have to contain
the needed information.
- [qa-bugs] [Bug 6707] Update: mumble new security issue CVE-2012-0863
- [qa-bugs] [Bug 5142] Backport: tremulous 3.0
This would mean more work for packagers and bugsquad to make sure the bug
report has a well-formatted summary.
Ideally, it would be good if we could see also from the mail subject what
version(s) of Mageia the update or backport is for, such as :
- [qa-bugs] [Bug 6707] Update: mumble new security issue CVE-2012-0863 [mga1]
- [qa-bugs] [Bug 5142] Backport: tremulous 3.0 [mga1][mga2]
What solution do you think we should choose? #1, #2, another one? And if we go
for solution #1 do you think we can still have the [mgaX] part (like was done
on some bugs already)?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mageia-bugsquad