summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-July/017245.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2012-July/017245.html')
-rw-r--r--zarb-ml/mageia-dev/2012-July/017245.html125
1 files changed, 125 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-July/017245.html b/zarb-ml/mageia-dev/2012-July/017245.html
new file mode 100644
index 000000000..bbfe6c208
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-July/017245.html
@@ -0,0 +1,125 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Clearing up updates Management
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Clearing%20up%20updates%20Management&In-Reply-To=%3C4FFB51F8.3030009%40mageia.org%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="017257.html">
+ <LINK REL="Next" HREF="017246.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Clearing up updates Management</H1>
+ <B>Anne Nicolas</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Clearing%20up%20updates%20Management&In-Reply-To=%3C4FFB51F8.3030009%40mageia.org%3E"
+ TITLE="[Mageia-dev] Clearing up updates Management">ennael at mageia.org
+ </A><BR>
+ <I>Mon Jul 9 23:49:44 CEST 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="017257.html">[Mageia-dev] RIP Eugeni Dodonov
+</A></li>
+ <LI>Next message: <A HREF="017246.html">[Mageia-dev] GUADEC - anyone going?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#17245">[ date ]</a>
+ <a href="thread.html#17245">[ thread ]</a>
+ <a href="subject.html#17245">[ subject ]</a>
+ <a href="author.html#17245">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>During tonight's council meeting, people agreed the following things to
+resolve the current situation with updates management.
+
+QA has had a difficult time since Mageia started, its main goal being to
+improve the overall quality and image of the Mageia distribution.
+
+We all recognise that security updates are more important than other
+fixes, but technically if another fix can be made at the same time, and
+the packager agrees, then it should be done. An extra build on the
+buildsystem + mirroring to the primary mirrors takes just a few hours so
+it is not much of a delay.
+
+For optimum quality it is ideal to apply the fix in both stable and
+cauldron. We have to recognise though that we won't always have
+resources to fix everything, so we also have to accept that not all bugs
+will be fixed on stable.
+
+Another difficulty for the QA team is that many packages are new to them
+too, so it is a steep learning curve, which leads to many questions.
+
+QA has done a good job of trying to balance priorities. We have known
+critical fixes to be pushed really quickly through QA when the update
+request was thoroughly following the updates procedure, and/or the
+packager asked for fast QA since he underlined the bug as being _really_
+critical
+
+Here is what was agreed upon at Council to help both packagers and QA
+teams to work properly, in harmony, and improve the general process. The
+QA team will ask anything needed on bugs they hit (remember end users
+can/will hit the same things) even during security validation. These
+questions should be hounored and responded to, either with a &quot;will fix
+now&quot;, &quot;will fix later&quot; or &quot;wont fix&quot; type response, adding reasons in
+case it can't be fixed right now.
+
+We all need to remember that every one of us is contributing of our own
+free time, and no one person's time is any more &quot;important&quot; than another's.
+
+This mail also means that we will have no more discussion on this topic
+and should now close all pending discussions about all this. As a last
+reminder, please keep in mind our code of conduct
+(<A HREF="http://www.mageia.org/en/about/code-of-conduct/">http://www.mageia.org/en/about/code-of-conduct/</A>). Disagreements of this
+nature should be raised at council and resolved amicably.
+
+To this end, this email has been written by council representatives from
+both teams, following the council discussion, and is being sent to both
+Packaging and QA team mailing lists. Let us all please abide by it and
+move forward in a positive direction.
+
+Cheers and thanks
+
+--
+Anne
+<A HREF="http://mageia.org">http://mageia.org</A>
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="017257.html">[Mageia-dev] RIP Eugeni Dodonov
+</A></li>
+ <LI>Next message: <A HREF="017246.html">[Mageia-dev] GUADEC - anyone going?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#17245">[ date ]</a>
+ <a href="thread.html#17245">[ thread ]</a>
+ <a href="subject.html#17245">[ subject ]</a>
+ <a href="author.html#17245">[ 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>