diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-January/011239.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-January/011239.html | 136 |
1 files changed, 136 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-January/011239.html b/zarb-ml/mageia-dev/2012-January/011239.html new file mode 100644 index 000000000..9bc7beeb8 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-January/011239.html @@ -0,0 +1,136 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] please stop doing "bugs" for updating magia 1 + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20please%20stop%20doing%20%22bugs%22%20for%20updating%20magia%201&In-Reply-To=%3CCAOPHaVTvkCAm0xB_0O9uArLRmqBQc92%2B7Wgjzv8EDjm_qa7cgg%40mail.gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="011238.html"> + <LINK REL="Next" HREF="011240.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] please stop doing "bugs" for updating magia 1</H1> + <B>Christian Lohmaier</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20please%20stop%20doing%20%22bugs%22%20for%20updating%20magia%201&In-Reply-To=%3CCAOPHaVTvkCAm0xB_0O9uArLRmqBQc92%2B7Wgjzv8EDjm_qa7cgg%40mail.gmail.com%3E" + TITLE="[Mageia-dev] please stop doing "bugs" for updating magia 1">lohmaier+mageia at googlemail.com + </A><BR> + <I>Wed Jan 11 17:48:28 CET 2012</I> + <P><UL> + <LI>Previous message: <A HREF="011238.html">[Mageia-dev] please stop doing "bugs" for updating magia 1 +</A></li> + <LI>Next message: <A HREF="011240.html">[Mageia-dev] please stop doing "bugs" for updating magia 1 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#11239">[ date ]</a> + <a href="thread.html#11239">[ thread ]</a> + <a href="subject.html#11239">[ subject ]</a> + <a href="author.html#11239">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Wed, Jan 11, 2012 at 4:51 PM, Guillaume Rousse +<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">guillomovitch at gmail.com</A>> wrote: +><i> Le 11/01/2012 16:09, Antoine Pitrou a écrit : +</I>><i> +</I>>><i> As a Mageia user I would expect Mageia to package significant *bugfix +</I>>><i> releases* and ship them in the updates for the stable distro. +</I>><i> +</I>><i> You'd rather read the current update policy, rather than expect blind +</I>><i> assertions: +</I>><i> <A HREF="https://wiki.mageia.org/en/Updates_policy">https://wiki.mageia.org/en/Updates_policy</A> +</I> +Whoa - this is a rather stupid policy. (my opinion, yours obviously differs). +"For the most part, an update should consist of a <bold>patched build +of the same version</bold> of the package released with the +distribution," + +Welcome to distro-isolation, putting burden on maintainers, giving +them all the reason to deny a reasonable request for a bugfix release +because it just is too much work to hunt for a specific commit that +fixed bug x. + +>><i> For example, it would be nice if an up-to-date Mageia 1 system had +</I>>><i> Python 2.7.2 rather than Python 2.7.1 (not a deal-breaker, of course, +</I>>><i> but nice). There's more than a hundred bug fixes between the two +</I>>><i> versions and I don't expect Mageia to have independently fixed many of +</I>>><i> these bugs. +</I>><i> +</I>><i> A bug may vary from a typo in a man page to a critical security update, +</I> +And a typo-fix is not worthwhile to have? + +><i> which make the number of claimed bugfix a poor decision metric. A +</I>><i> non-regression ensurance would be a better one, but it's quite difficult to +</I>><i> assert. +</I> +Don't assume all upstream projects are a bunch of clueless idiots. + +For upstream releases that have a clear version/release scheme, with +micro releases being compatible bugfixes only, the above mentioned +policy is completely nonsense, same for your fear of regressions, etc. + +Sure, you cannot be save of regressions, but what makes you think you +are smarter than upstream? What makes you so sure that not the one +commit you add as a patch to your package is the one that causes the +regressions? + +Regressions have the nice habit of being triggered by changes in +apparently unrelated code... + +My 0.02€ only, but I strongly suggest for that update policy to be clarified. +When there is no dedicated bugfix release procedure in the upstream +package, an update is a rebuild of the same version with a +corresponding patch. That's reasonable (as opposed to using a newer +minor or even major release, those are backports). +But once again: if upstream has a major.minor.micro scheme with micro +versions being bugfix releases, I really don't see any sane reason for +not "allowing" those updates. + +ciao +Christian +</PRE> + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="011238.html">[Mageia-dev] please stop doing "bugs" for updating magia 1 +</A></li> + <LI>Next message: <A HREF="011240.html">[Mageia-dev] please stop doing "bugs" for updating magia 1 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#11239">[ date ]</a> + <a href="thread.html#11239">[ thread ]</a> + <a href="subject.html#11239">[ subject ]</a> + <a href="author.html#11239">[ 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> |