diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-June/016479.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-June/016479.html | 122 |
1 files changed, 122 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016479.html b/zarb-ml/mageia-dev/2012-June/016479.html new file mode 100644 index 000000000..6ae8bd871 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016479.html @@ -0,0 +1,122 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] QA bugs for MGA1 and MGA2 + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20QA%20bugs%20for%20MGA1%20and%20MGA2&In-Reply-To=%3C4FD8F6A2.1050809%40gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="016469.html"> + <LINK REL="Next" HREF="016496.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] QA bugs for MGA1 and MGA2</H1> + <B>Claire Robinson</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20QA%20bugs%20for%20MGA1%20and%20MGA2&In-Reply-To=%3C4FD8F6A2.1050809%40gmail.com%3E" + TITLE="[Mageia-dev] QA bugs for MGA1 and MGA2">eeeemail at gmail.com + </A><BR> + <I>Wed Jun 13 22:22:58 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="016469.html">[Mageia-dev] [changelog] [RPM] 2 core/updates_testing gambas3-3.1.1-1.1.mga2 +</A></li> + <LI>Next message: <A HREF="016496.html">[Mageia-dev] QA bugs for MGA1 and MGA2 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16479">[ date ]</a> + <a href="thread.html#16479">[ thread ]</a> + <a href="subject.html#16479">[ subject ]</a> + <a href="author.html#16479">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Morning Dev + +This is just a follow up email after the packagers meeting on behalf of QA. + + +* At packagers request we have recently been trialling the use of one +bug report where updates cover both releases. So mga1 and mga2 on the +same bug. So far it has been working quite well. Complex ones like php +have been using two bugs so if you do this please use common sense as to +whether it needs two (or more) or could be put onto one. + +One which should really have been split was the recent postgresql update +where 8.4 & 9.0 for mga1 and 8.4 9.0 & 9.1 for mga2 were all on one bug +report. It could have been better with one for each version. Luckily +there was nothing wrong and validating went without a hitch but if +something was wrong then it would have been very difficult to keep track. + +* As we are now mostly using one bug report for this type of update we +need a simple way to be able to spot those bugs. With current bugzilla +it is not possible to set multiple releases. We'd appreciate if you +could follow the bugsquad policy for this. + +It is quite simple and elegant really. Set the 'Version' to 2 and add +MGA1TOO into the 'Whiteboard'. + +Doing so will enable QA to see straight away that the bug has updates +for both releases. + +In the meeting an action was set with the wrong keyword 'MGA2TOO' so +please ignore that, it should be 'MGA1TOO' as 'Version' will already be +set to '2'. + +Much appreciated +Thankyou +Claire (MrsB) +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="016469.html">[Mageia-dev] [changelog] [RPM] 2 core/updates_testing gambas3-3.1.1-1.1.mga2 +</A></li> + <LI>Next message: <A HREF="016496.html">[Mageia-dev] QA bugs for MGA1 and MGA2 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16479">[ date ]</a> + <a href="thread.html#16479">[ thread ]</a> + <a href="subject.html#16479">[ subject ]</a> + <a href="author.html#16479">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |