diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-September/008555.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-September/008555.html | 116 |
1 files changed, 116 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-September/008555.html b/zarb-ml/mageia-dev/2011-September/008555.html new file mode 100644 index 000000000..5fcaeda41 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-September/008555.html @@ -0,0 +1,116 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Opening backports (was Re: [Mageia-sysadm] Using SQL database for youri) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Opening%20backports%20%28was%20Re%3A%20%5BMageia-sysadm%5D%20Using%0A%09SQL%20database%20for%20youri%29&In-Reply-To=%3C201109302335.40821.stormi%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="008507.html"> + <LINK REL="Next" HREF="008497.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Opening backports (was Re: [Mageia-sysadm] Using SQL database for youri)</H1> + <B>Samuel Verschelde</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Opening%20backports%20%28was%20Re%3A%20%5BMageia-sysadm%5D%20Using%0A%09SQL%20database%20for%20youri%29&In-Reply-To=%3C201109302335.40821.stormi%40laposte.net%3E" + TITLE="[Mageia-dev] Opening backports (was Re: [Mageia-sysadm] Using SQL database for youri)">stormi at laposte.net + </A><BR> + <I>Fri Sep 30 23:35:40 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="008507.html">[Mageia-dev] Opening backports (was Re: [Mageia-sysadm] Using SQL database for youri) +</A></li> + <LI>Next message: <A HREF="008497.html">[Mageia-dev] [changelog] [RPM] cauldron core/release zoom-1.1.4-2.mga2 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#8555">[ date ]</a> + <a href="thread.html#8555">[ thread ]</a> + <a href="subject.html#8555">[ subject ]</a> + <a href="author.html#8555">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le jeudi 29 septembre 2011 21:10:42, Samuel Verschelde a écrit : +><i> Le jeudi 29 septembre 2011 20:55:43, Florian Hubold a écrit : +</I>><i> > Am 29.09.2011 14:13, schrieb Olav Vitters: +</I>><i> > > On Thu, Sep 29, 2011 at 10:24:56AM +0200, Samuel Verschelde wrote: +</I>><i> > >> backports_testing, but it means that we would lose the current +</I>><i> > >> checking that updates come from the 1/updates branch) +</I>><i> > > +</I>><i> > > Long term I prefer more checks because I do make mistakes. But maybe +</I>><i> > > lax as a temporary ("a few weeks") solution until it uses the SQL +</I>><i> > > database? +</I>><i> > +</I>><i> > Well, is it really that necessary for a matter of some weeks to speed up +</I>><i> > backports opening? Shouldn't we care first that sustainability of Mageia +</I>><i> > is ensured first? +</I>><i> > +</I>><i> > It's not like backports candidates will lessen workload on QA, rather the +</I>><i> > opposite. That's my personal opinion. +</I>><i> +</I>><i> Some genuine user needs can only be covered by backports per our policy, I +</I>><i> don't see why we should wait more (already 4 months since the release of +</I>><i> Mageia 1). QA team already said it's ready to test backports, and if we +</I>><i> have difficulty we simply will find means to get more testers. Also, +</I>><i> updates will still remain the priority. +</I>><i> +</I>><i> Opening backports media does not mean that we will start backporting +</I>><i> everything. But a policy has been chosen, after a loooooooooong debate, and +</I>><i> there seems to be a simple way to open those media to package submitting. +</I>><i> +</I>><i> Also, the sooner we have backports, the less there will be external third- +</I>><i> party repos with all the problems (upgrade, support) that causes. There +</I>><i> already are, don't let them too much space and rather invite their +</I>><i> packagers to backport *inside* (as long as they stay within the policy of +</I>><i> course). +</I>><i> +</I>><i> About Mageia's sustainability, we already are working to that (QA team is +</I>><i> operational, package adoption campaign is undergoing...), and having +</I>><i> backports media won't prevent us from continuing. +</I>><i> +</I>><i> Also, the "few weeks" is a really vague estimation, my guess is it risks to +</I>><i> be rather months because sysadmins seem to have a big TODO list a little +</I>><i> resources. That's why I'm proposing 2 "technically simple" ways to move +</I>><i> forward. +</I>><i> +</I>><i> Best regards +</I>><i> +</I>><i> Samuel Verschelde +</I> +If needed, the tremendous amount of packages in Blogdrake's 3rd party media +shows how much backports are needed by users, whatever we as packagers can +think of it. + +I'm still convinced that opening backports right now, using one of my 2 +proposals (if I haven't overlooked a technical difficulty), would be an +important step forward for us. + +Best regards + +Samuel +</PRE> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="008507.html">[Mageia-dev] Opening backports (was Re: [Mageia-sysadm] Using SQL database for youri) +</A></li> + <LI>Next message: <A HREF="008497.html">[Mageia-dev] [changelog] [RPM] cauldron core/release zoom-1.1.4-2.mga2 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#8555">[ date ]</a> + <a href="thread.html#8555">[ thread ]</a> + <a href="subject.html#8555">[ subject ]</a> + <a href="author.html#8555">[ 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> |