diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-March/012801.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-March/012801.html | 115 |
1 files changed, 115 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-March/012801.html b/zarb-ml/mageia-dev/2012-March/012801.html new file mode 100644 index 000000000..77117c041 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-March/012801.html @@ -0,0 +1,115 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Release_blocker bugs + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Release_blocker%20bugs&In-Reply-To=%3C1331195836.1167.1.camel%40liliana.cdg.redhat.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="012789.html"> + <LINK REL="Next" HREF="012904.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Release_blocker bugs</H1> + <B>Michael Scherer</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Release_blocker%20bugs&In-Reply-To=%3C1331195836.1167.1.camel%40liliana.cdg.redhat.com%3E" + TITLE="[Mageia-dev] Release_blocker bugs">misc at zarb.org + </A><BR> + <I>Thu Mar 8 09:37:16 CET 2012</I> + <P><UL> + <LI>Previous message: <A HREF="012789.html">[Mageia-dev] Release_blocker bugs +</A></li> + <LI>Next message: <A HREF="012904.html">[Mageia-dev] Release_blocker bugs +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#12801">[ date ]</a> + <a href="thread.html#12801">[ thread ]</a> + <a href="subject.html#12801">[ subject ]</a> + <a href="author.html#12801">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le mercredi 07 mars 2012 à 21:43 +0100, Manuel Hiebel a écrit : +><i> Hello, +</I>><i> +</I>><i> How can we (the bugsquad or other people) determinate what can be a +</I>><i> release_blocker bug ? +</I>><i> +</I>><i> in the triage guide we can see: +</I>><i> +</I>><i> "The release_blocker priority is only relevant to bugs filed on Cauldron +</I>><i> or beta releases, and should only be used for issues which are +</I>><i> sufficiently critical that it would severely impair the overall quality +</I>><i> of a release if it were made available without the issue being +</I>><i> resolved." +</I>><i> +</I>><i> That is not clear for me. And the only mail relating to that, was from +</I>><i> Anne in May and not useful for me. +</I> +I would say "stuff that cannot be fixed after release" would be release +blocker. Not to say that the rest cannot be too, but at least, that's +the first criteria. + +So a software on livecd that crash on startup would also be a blocker. + +-- +Michael Scherer + +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="012789.html">[Mageia-dev] Release_blocker bugs +</A></li> + <LI>Next message: <A HREF="012904.html">[Mageia-dev] Release_blocker bugs +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#12801">[ date ]</a> + <a href="thread.html#12801">[ thread ]</a> + <a href="subject.html#12801">[ subject ]</a> + <a href="author.html#12801">[ 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> |