diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/005228.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-June/005228.html | 97 |
1 files changed, 97 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/005228.html b/zarb-ml/mageia-dev/2011-June/005228.html new file mode 100644 index 000000000..5cf38e987 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/005228.html @@ -0,0 +1,97 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Finalizing update process + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Finalizing%20update%20process&In-Reply-To=%3C1307582142.26948.83.camel%40akroma.ephaone.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="005226.html"> + <LINK REL="Next" HREF="005232.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Finalizing update process</H1> + <B>Michael Scherer</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Finalizing%20update%20process&In-Reply-To=%3C1307582142.26948.83.camel%40akroma.ephaone.org%3E" + TITLE="[Mageia-dev] Finalizing update process">misc at zarb.org + </A><BR> + <I>Thu Jun 9 03:15:42 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="005226.html">[Mageia-dev] Finalizing update process +</A></li> + <LI>Next message: <A HREF="005232.html">[Mageia-dev] Finalizing update process +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5228">[ date ]</a> + <a href="thread.html#5228">[ thread ]</a> + <a href="subject.html#5228">[ subject ]</a> + <a href="author.html#5228">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le jeudi 09 juin 2011 à 02:40 +0300, Ahmad Samir a écrit : + +><i> Yes, but I was talking about the actual submitting to */release, not +</I>><i> fixing the package itself. IIUC the submission rights will be +</I>><i> restricted to the Sec team. +</I> +Sorry to be picky, but there is no submit to */release, it is frozen. +And in my proposition, there is also no submit to */update, there is a +move from */updates_testing. + +So for managing the submit to updates_testing and the whole process, I +think it should be open to any packagers. It should be maintainers +responsibility to do the update ( prepare, do a test build, check, +submit ), even if secteam members could be proactive for that. But the +process should not be restricted to them, or it will not scale ( and +given we want to have bugfixes updates, it wouldn't make much sense to +call the team like this ). + +Since ensuring that a update is a minimal change is (to me) a quality +issue, I propose to add to the QA list of things to check before +refusing a update : +"it doesn't fullfill the requirement of minimal changes ( with +exceptions" + +But that requires QA people to have minimal packaging notions, which +could be a problem :/ + +Again, nothing prevent people from the secteam to also be part of the QA +team. +-- +Michael Scherer + +</PRE> + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="005226.html">[Mageia-dev] Finalizing update process +</A></li> + <LI>Next message: <A HREF="005232.html">[Mageia-dev] Finalizing update process +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5228">[ date ]</a> + <a href="thread.html#5228">[ thread ]</a> + <a href="subject.html#5228">[ subject ]</a> + <a href="author.html#5228">[ 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> |