diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-bugsquad/2012-July/000148.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-bugsquad/2012-July/000148.html')
| -rw-r--r-- | zarb-ml/mageia-bugsquad/2012-July/000148.html | 103 |
1 files changed, 103 insertions, 0 deletions
diff --git a/zarb-ml/mageia-bugsquad/2012-July/000148.html b/zarb-ml/mageia-bugsquad/2012-July/000148.html new file mode 100644 index 000000000..2961e1eca --- /dev/null +++ b/zarb-ml/mageia-bugsquad/2012-July/000148.html @@ -0,0 +1,103 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-bugsquad] Differentiate mails concerning update candidates and backports candidates (and ideally mga1/2) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-bugsquad%40mageia.org?Subject=Re%3A%20%5BMageia-bugsquad%5D%20Differentiate%20mails%20concerning%20update%20candidates%0A%09and%20backports%20candidates%20%28and%20ideally%20mga1/2%29&In-Reply-To=%3C201207052234.53238.stormi%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="000147.html"> + <LINK REL="Next" HREF="000149.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-bugsquad] Differentiate mails concerning update candidates and backports candidates (and ideally mga1/2)</H1> + <B>Samuel Verschelde</B> + <A HREF="mailto:mageia-bugsquad%40mageia.org?Subject=Re%3A%20%5BMageia-bugsquad%5D%20Differentiate%20mails%20concerning%20update%20candidates%0A%09and%20backports%20candidates%20%28and%20ideally%20mga1/2%29&In-Reply-To=%3C201207052234.53238.stormi%40laposte.net%3E" + TITLE="[Mageia-bugsquad] Differentiate mails concerning update candidates and backports candidates (and ideally mga1/2)">stormi at laposte.net + </A><BR> + <I>Thu Jul 5 22:34:53 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="000147.html">[Mageia-bugsquad] Fwd: Re: [Mageia-dev] net_applet segfaulting +</A></li> + <LI>Next message: <A HREF="000149.html">[Mageia-bugsquad] Differentiate mails concerning update candidates and backports candidates (and ideally mga1/2) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#148">[ date ]</a> + <a href="thread.html#148">[ thread ]</a> + <a href="subject.html#148">[ subject ]</a> + <a href="author.html#148">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hi, + +Here at QA the bugzilla notifications we get at <A HREF="https://www.mageia.org/mailman/listinfo/mageia-bugsquad">qa-bugs at ml.mageia.org</A> 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 +other ideas. + + +*** 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. + +Example: +- [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)? + +Best regards +Samuel Verschelde +-------------- next part -------------- +An HTML attachment was scrubbed... +URL: </pipermail/mageia-bugsquad/attachments/20120705/5d970740/attachment.html> +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000147.html">[Mageia-bugsquad] Fwd: Re: [Mageia-dev] net_applet segfaulting +</A></li> + <LI>Next message: <A HREF="000149.html">[Mageia-bugsquad] Differentiate mails concerning update candidates and backports candidates (and ideally mga1/2) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#148">[ date ]</a> + <a href="thread.html#148">[ thread ]</a> + <a href="subject.html#148">[ subject ]</a> + <a href="author.html#148">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-bugsquad">More information about the Mageia-bugsquad +mailing list</a><br> +</body></html> |