summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-January/011290.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2012-January/011290.html')
-rw-r--r--zarb-ml/mageia-dev/2012-January/011290.html126
1 files changed, 126 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-January/011290.html b/zarb-ml/mageia-dev/2012-January/011290.html
new file mode 100644
index 000000000..8d721ecc0
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-January/011290.html
@@ -0,0 +1,126 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] please stop doing &quot;bugs&quot; 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=%3C201201121729.44056.bgmilne%40zarb.org%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="011288.html">
+ <LINK REL="Next" HREF="011247.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] please stop doing &quot;bugs&quot; for updating magia 1</H1>
+ <B>Buchan Milne</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=%3C201201121729.44056.bgmilne%40zarb.org%3E"
+ TITLE="[Mageia-dev] please stop doing &quot;bugs&quot; for updating magia 1">bgmilne at zarb.org
+ </A><BR>
+ <I>Thu Jan 12 16:29:43 CET 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="011288.html">[Mageia-dev] please stop doing &quot;bugs&quot; for updating magia 1
+</A></li>
+ <LI>Next message: <A HREF="011247.html">[Mageia-dev] please stop doing &quot;bugs&quot; for updating magia 1
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#11290">[ date ]</a>
+ <a href="thread.html#11290">[ thread ]</a>
+ <a href="subject.html#11290">[ subject ]</a>
+ <a href="author.html#11290">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>On Thursday, 12 January 2012 16:45:39 Johnny A. Solbu wrote:
+&gt;<i> On Thursday 12 January 2012 10:05, Buchan Milne wrote:
+</I>&gt;<i> &gt; many users don't report upstream
+</I>&gt;<i> &gt; bugs to the distro's tracker.&#8221;
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; Why not?
+</I>&gt;<i>
+</I>&gt;<i> Why should they? As far as the average Joe is concerned they should only
+</I>&gt;<i> have to file a bug one place. This is how many of them think. And I agree
+</I>&gt;<i> with them.
+</I>&gt;<i>
+</I>&gt;<i> &gt; 1)File a bug with the distribution, and have the distribution worry about
+</I>&gt;<i> &gt; reporting or fixing the bug and providing an update
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; 2)File a bug upstream, when the bug is fixed uptream, file a bug with the
+</I>&gt;<i> &gt; distributor, referencing the upstream bug
+</I>&gt;<i>
+</I>&gt;<i> My experience is that if they file a bug report in the first place, they
+</I>&gt;<i> Either contact the upstream developer or the distribution's bugzilla team.
+</I>
+I covered this in (1).
+
+&gt;<i> They never do both, as they believe that doing both is a waste of time,
+</I>&gt;<i> since the fixed version eventually find it's way to the distribution
+</I>&gt;<i> anyway.
+</I>
+Sure, it will, on the next release of the distribution, assuming the new
+upstream release was before version freeze.
+
+&gt;<i> &gt; An approach that doens't include a bug filed with the distribution means
+</I>&gt;<i> &gt; the user doesn't really seem interested in receiving an update from the
+</I>&gt;<i> &gt; distribution.
+</I>&gt;<i>
+</I>&gt;<i> Incorrect assumption.
+</I>&gt;<i> As someone who is the support service for some users I have some experience
+</I>&gt;<i> with this. They assume that any serious bug will be fixed in one of the
+</I>&gt;<i> next releaces,
+</I>
+But this *is* the case. What we are talking about *here*, is that the bugfix
+update be shipped to old releases.
+
+&gt;<i> because that's how it works with Microsoft.
+</I>
+Yes, non-critical release will be shipped in next SP, a year or so later.
+
+&gt;<i> And they
+</I>&gt;<i> haven't heard of anyone filing any bug at Microsoft.
+</I>
+Just because they haven't, doesn't mean it doesn't happen.
+
+&gt;<i> The bugs just get
+</I>&gt;<i> fixed without them ever repporting anything, and they assume that this is
+</I>&gt;<i> how things are supposed to work. Sometimes they even think that what we
+</I>&gt;<i> consider as bugs, they believe it is how things are supposed to work.
+</I>&gt;<i>
+</I>&gt;<i> If they're not happy with how the system works, they often conclude that
+</I>&gt;<i> Linux Sucks Ass, and move back to Windows or OS X.
+</I>
+But, your comparison is invalid. Users must pay for the privilege of upgrading
+to get non-critical bugfixes the latter, and wait quite some time for the
+former.
+
+Regards,
+Buchan
+</PRE>
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="011288.html">[Mageia-dev] please stop doing &quot;bugs&quot; for updating magia 1
+</A></li>
+ <LI>Next message: <A HREF="011247.html">[Mageia-dev] please stop doing &quot;bugs&quot; for updating magia 1
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#11290">[ date ]</a>
+ <a href="thread.html#11290">[ thread ]</a>
+ <a href="subject.html#11290">[ subject ]</a>
+ <a href="author.html#11290">[ 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>