summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-July/006446.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2011-July/006446.html')
-rw-r--r--zarb-ml/mageia-dev/2011-July/006446.html152
1 files changed, 152 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-July/006446.html b/zarb-ml/mageia-dev/2011-July/006446.html
new file mode 100644
index 000000000..7fba567b6
--- /dev/null
+++ b/zarb-ml/mageia-dev/2011-July/006446.html
@@ -0,0 +1,152 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Updates process is now available
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Updates%20process%20is%20now%20available&In-Reply-To=%3C20110707155704.GX21938%40mars-attacks.org%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="006444.html">
+ <LINK REL="Next" HREF="006868.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Updates process is now available</H1>
+ <B>nicolas vigier</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Updates%20process%20is%20now%20available&In-Reply-To=%3C20110707155704.GX21938%40mars-attacks.org%3E"
+ TITLE="[Mageia-dev] Updates process is now available">boklm at mars-attacks.org
+ </A><BR>
+ <I>Thu Jul 7 17:57:04 CEST 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="006444.html">[Mageia-dev] Updates process is now available
+</A></li>
+ <LI>Next message: <A HREF="006868.html">[Mageia-dev] Updates process is now available
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#6446">[ date ]</a>
+ <a href="thread.html#6446">[ thread ]</a>
+ <a href="subject.html#6446">[ subject ]</a>
+ <a href="author.html#6446">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>On Thu, 07 Jul 2011, Damien Lallement wrote:
+
+&gt;<i> Le 07/07/2011 14:42, nicolas vigier a &#233;crit :
+</I>&gt;&gt;<i> On Tue, 21 Jun 2011, Damien Lallement wrote:
+</I>&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> Hello all,
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> security, qa and sysadmin team worked on the qa/updates process to provide
+</I>&gt;&gt;&gt;<i> updates as soon as possible.
+</I>&gt;&gt;&gt;<i> All is now ready (boklm is finalizing a scrip to move updates from
+</I>&gt;&gt;&gt;<i> &quot;testing&quot; to &quot;updates&quot;). This script will be uses by security team members
+</I>&gt;&gt;&gt;<i> and a few QA people to push updates.
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> You can now read:
+</I>&gt;&gt;&gt;<i> - <A HREF="http://www.mageia.org/wiki/doku.php?id=updates_policy">http://www.mageia.org/wiki/doku.php?id=updates_policy</A>
+</I>&gt;&gt;&gt;<i> - <A HREF="http://www.mageia.org/wiki/doku.php?id=qa_updates">http://www.mageia.org/wiki/doku.php?id=qa_updates</A>
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> I have some questions about updates process :
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> The page says to assign bug after validation :
+</I>&gt;&gt;<i> Assign the bug to <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">security at groups.mageia.org</A> if it's a security update
+</I>&gt;&gt;<i> (check that <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">qa-bugs at ml.mageia.org</A> is in 'CC')
+</I>&gt;&gt;<i> Let it assigned to <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">qa-bugs at ml.mageia.org</A> if it's a standard update
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Is it usefull to assign differently for security and non-security
+</I>&gt;&gt;<i> updates ?
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Could we add a keyword &quot;validated_update&quot; to bugs that are ready to be
+</I>&gt;&gt;<i> moved to updates, so they can be found easily ?
+</I>&gt;<i>
+</I>&gt;<i> I just write this because that's what was discuss on the meeting at this
+</I>&gt;<i> time with misc, ennael, stew and I (you were here too IIRC).
+</I>&gt;<i> We can discuss this point again if needed. :-)
+</I>&gt;<i>
+</I>&gt;<i> The idea was just not to assign package to secteam if not a secteam update
+</I>&gt;<i> (not to distrub them for standard packages).
+</I>
+Yes, but what is the difference between pushing standard update, and
+security update, after qa is done, and why should we disturb them for
+security updates, and not for standard updates ?
+
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="006444.html">[Mageia-dev] Updates process is now available
+</A></li>
+ <LI>Next message: <A HREF="006868.html">[Mageia-dev] Updates process is now available
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#6446">[ date ]</a>
+ <a href="thread.html#6446">[ thread ]</a>
+ <a href="subject.html#6446">[ subject ]</a>
+ <a href="author.html#6446">[ 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>