1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
|
<!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=%3CCA%2BCX%2Bbj7TxvdAVVULP7_yPn0xi80gW4YjDYjyWq64CM3veabTA%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="011239.html">
<LINK REL="Next" HREF="011241.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] please stop doing "bugs" for updating magia 1</H1>
<B>Pascal Terjan</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=%3CCA%2BCX%2Bbj7TxvdAVVULP7_yPn0xi80gW4YjDYjyWq64CM3veabTA%40mail.gmail.com%3E"
TITLE="[Mageia-dev] please stop doing "bugs" for updating magia 1">pterjan at gmail.com
</A><BR>
<I>Wed Jan 11 17:54:57 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="011239.html">[Mageia-dev] please stop doing "bugs" for updating magia 1
</A></li>
<LI>Next message: <A HREF="011241.html">[Mageia-dev] please stop doing "bugs" for updating magia 1
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#11240">[ date ]</a>
<a href="thread.html#11240">[ thread ]</a>
<a href="subject.html#11240">[ subject ]</a>
<a href="author.html#11240">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Wed, Jan 11, 2012 at 16:48, Christian Lohmaier
<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">lohmaier+mageia at googlemail.com</A>> wrote:
><i> On Wed, Jan 11, 2012 at 4:51 PM, Guillaume Rousse
</I>><i> <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">guillomovitch at gmail.com</A>> wrote:
</I>>><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>><i>
</I>><i> Whoa - this is a rather stupid policy. (my opinion, yours obviously differs).
</I>><i> "For the most part, an update should consist of a <bold>patched build
</I>><i> of the same version</bold> of the package released with the
</I>><i> distribution,"
</I>><i>
</I>><i> Welcome to distro-isolation, putting burden on maintainers, giving
</I>><i> them all the reason to deny a reasonable request for a bugfix release
</I>><i> because it just is too much work to hunt for a specific commit that
</I>><i> fixed bug x.
</I>><i>
</I>>>><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>><i>
</I>><i> And a typo-fix is not worthwhile to have?
</I>><i>
</I>>><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>><i>
</I>><i> Don't assume all upstream projects are a bunch of clueless idiots.
</I>
Don't assume the opposite either, it really depend on each project.
><i> For upstream releases that have a clear version/release scheme, with
</I>><i> micro releases being compatible bugfixes only, the above mentioned
</I>><i> policy is completely nonsense, same for your fear of regressions, etc.
</I>
Yes, bugfix only release have always been accepted, this should be
added to the exceptions on the wiki.
><i> Sure, you cannot be save of regressions, but what makes you think you
</I>><i> are smarter than upstream? What makes you so sure that not the one
</I>><i> commit you add as a patch to your package is the one that causes the
</I>><i> regressions?
</I>
Because the most changes you had, the most likely a regression is
><i> Regressions have the nice habit of being triggered by changes in
</I>><i> apparently unrelated code...
</I>><i>
</I>><i> My 0.02€ only, but I strongly suggest for that update policy to be clarified.
</I>><i> When there is no dedicated bugfix release procedure in the upstream
</I>><i> package, an update is a rebuild of the same version with a
</I>><i> corresponding patch. That's reasonable (as opposed to using a newer
</I>><i> minor or even major release, those are backports).
</I>><i> But once again: if upstream has a major.minor.micro scheme with micro
</I>><i> versions being bugfix releases, I really don't see any sane reason for
</I>><i> not "allowing" those updates.
</I>
Yes, they are actually allowed.
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="011239.html">[Mageia-dev] please stop doing "bugs" for updating magia 1
</A></li>
<LI>Next message: <A HREF="011241.html">[Mageia-dev] please stop doing "bugs" for updating magia 1
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#11240">[ date ]</a>
<a href="thread.html#11240">[ thread ]</a>
<a href="subject.html#11240">[ subject ]</a>
<a href="author.html#11240">[ 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>
|
