diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101021/001309.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101021/001309.html | 141 |
1 files changed, 141 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101021/001309.html b/zarb-ml/mageia-dev/20101021/001309.html new file mode 100644 index 000000000..bae552989 --- /dev/null +++ b/zarb-ml/mageia-dev/20101021/001309.html @@ -0,0 +1,141 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] How will be the realese cycle? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20will%20be%20the%20realese%20cycle%3F&In-Reply-To=%3C4CBFA9E6.2050109%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001314.html"> + <LINK REL="Next" HREF="001310.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] How will be the realese cycle?</H1> + <B>andré</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20will%20be%20the%20realese%20cycle%3F&In-Reply-To=%3C4CBFA9E6.2050109%40laposte.net%3E" + TITLE="[Mageia-dev] How will be the realese cycle?">andr55 at laposte.net + </A><BR> + <I>Thu Oct 21 04:48:06 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001314.html">[Mageia-dev] Mirror tree structure +</A></li> + <LI>Next message: <A HREF="001310.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1309">[ date ]</a> + <a href="thread.html#1309">[ thread ]</a> + <a href="subject.html#1309">[ subject ]</a> + <a href="author.html#1309">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Tux99 a écrit : +><i> +</I>><i> +</I>><i> Quote: Ahmad Samir wrote on Thu, 14 October 2010 16:00 +</I>><i> +</I>>><i> I've seen, too many times, trigger-happy packagers backporting +</I>>><i> packages that're not maintained by them (so they know it less than +</I>>><i> those package maintainer(s)), breaking those packages and annoying the +</I>>><i> maintainers of said packages. It's usually irresponsible to backport a +</I>>><i> package without taking that package maintainer's opinion into account. +</I>>><i> (an infamous example on that is gwibber being backported to 2010.1). +</I>>><i> +</I>><i> I agree it should be preferably the maintainer doing the backport, or he +</I>><i> should at least be consulted. +</I>><i> +</I>I think that should be an explicit policy of Mageia. +><i> +</I>><i> +</I>>><i> New users who frequented the forums always got to know what backports +</I>>><i> are pretty fast. And bugzilla is the perfect system for asking for a +</I>>><i> backport, that worked pretty good. +</I>>><i> +</I>><i> The wast majority of 'normal' users never uses the forum. +</I>><i> Backports shouldn't be something that only users who frequent the forum +</I>><i> find out about. +</I>><i> +</I>True. Although I suspect that they are more likely to use the forum +than formally make a bug report. +>><i> That's they way backports has always worked, no specific patches, just +</I>>><i> the latest cooker package pushed to backports "as is with no official +</I>>><i> support", that's reasonable, packagers shouldn't promise to support +</I>>><i> backports when they can't due to various reasons (time, effort.. etc). +</I>>><i> +</I>><i> But IMHO that should change in Mageia, we should promise support by the way +</I>><i> of timely updates, especially when security issues are present. +</I>><i> +</I>That can only change if we have more ressources. At least at first, we +risk to have somewhat less, without the financial input from the +commercial side that exists for Mandriva. +>>><i> Backports shouldn't be second choice, it should be the default, +</I>>>><i> since that +</I>>>><i> would make Mageia stand out from other distros as being the distro +</I>>>><i> were +</I>>>><i> users get the latest versions of apps before any other major +</I>>>><i> distro +</I>>>><i> provides them. +</I>>>><i> +</I>>><i> Enabling them by default defies the purpose of having backports at +</I>>><i> all; it's not for new users, it's more for slightly experienced users +</I>>><i> or power users who want the latest versions of apps. +</I>>><i> +</I>Agreed. +><i> That's exactly the crucial bit that IMHO needs to change, backports are +</I>><i> very interesting for 'normal' users so we should make sure normal users +</I>><i> can use them. +</I>><i> Don't you see how attractive it is especially for 'normal' users to have +</I>><i> access to the latest versions all the time? +</I>><i> +</I>I would expect that 'normal' users would be most concerned that the +system just work. +The 'latest versions' is more a preoccupation of a minority of at least +moderately experienced users, who probably also like trying out all +sorts of new software. +Not at all typical of the population in general, but admittedly more +common among Linux users. + +><i> Sure, not everyone wants them, but by integrating the skip.list in the +</I>><i> update GUI we could keep 'conservative' users happy too +</I>That would certainly help, and not just for 'conservative' users. Often +a particular package only has problems on some systems. A more readily +accessible skip.list blacklist would make it easier to avoid accidently +re-installing a package that didn't work as expected the first time, for +whatever reason. + +- André (andre999) +</PRE> + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001314.html">[Mageia-dev] Mirror tree structure +</A></li> + <LI>Next message: <A HREF="001310.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1309">[ date ]</a> + <a href="thread.html#1309">[ thread ]</a> + <a href="subject.html#1309">[ subject ]</a> + <a href="author.html#1309">[ 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> |