From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2012-March/012801.html | 115 ++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-March/012801.html (limited to 'zarb-ml/mageia-dev/2012-March/012801.html') 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 @@ + + + + [Mageia-dev] Release_blocker bugs + + + + + + + + + +

[Mageia-dev] Release_blocker bugs

+ Michael Scherer + misc at zarb.org +
+ Thu Mar 8 09:37:16 CET 2012 +

+
+ +
Le mercredi 07 mars 2012 à 21:43 +0100, Manuel Hiebel a écrit :
+> Hello,
+> 
+> How can we (the bugsquad or other people) determinate what can be a
+> release_blocker bug ?
+> 
+> in the triage guide we can see:
+> 
+> "The release_blocker priority is only relevant to bugs filed on Cauldron
+> or beta releases, and should only be used for issues which are
+> sufficiently critical that it would severely impair the overall quality
+> of a release if it were made available without the issue being
+> resolved."
+> 
+> That is not clear for me. And the only mail relating to that, was from
+> Anne in May and not useful for me.
+
+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
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1