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
|
<!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=%3C4F0F37AD.3060702%40arcor.de%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="011336.html">
<LINK REL="Next" HREF="011306.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] please stop doing "bugs" for updating magia 1</H1>
<B>Florian Hubold</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=%3C4F0F37AD.3060702%40arcor.de%3E"
TITLE="[Mageia-dev] please stop doing "bugs" for updating magia 1">doktor5000 at arcor.de
</A><BR>
<I>Thu Jan 12 20:42:37 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="011336.html">[Mageia-dev] please stop doing "bugs" for updating magia 1
</A></li>
<LI>Next message: <A HREF="011306.html">[Mageia-dev] please stop doing "bugs" for updating magia 1
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#11300">[ date ]</a>
<a href="thread.html#11300">[ thread ]</a>
<a href="subject.html#11300">[ subject ]</a>
<a href="author.html#11300">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Am 12.01.2012 19:01, schrieb Christian Lohmaier:
><i> Hi Juan Luis,
</I>><i>
</I>><i> On Wed, Jan 11, 2012 at 10:09 PM, Juan Luis Baptiste <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">juancho at mageia.org</A>> wrote:
</I>>><i> [..]
</I>>><i> As I said, no one is talking about picking up a fix if there's a bug
</I>>><i> fix only release, it's for when it isn't and we need to reduce the
</I>>><i> chance of regressions by taking the modifications that *exactly* fix
</I>>><i> that bug.
</I>><i> I strongly disagree. The policy is stating the exact opposite. And
</I>><i> also Michael seems to defend the policy as it is written, and not your
</I>><i> interpretation here.
</I>><i>
</I>><i> That again you might have a different understanding of
</I>><i> bugfix-only-release. I think I stated mine often enough (increase in
</I>><i> micro version when package follows major.minor.micro versioning scheme
</I>><i> and no new features are introduced in micro releases).
</I>><i>
</I>><i> So please change the wording of the update policy accordingly
</I>><i> <A HREF="https://wiki.mageia.org/en/Updates_policy">https://wiki.mageia.org/en/Updates_policy</A> reads:
</I>><i> ##########
</I>><i> For the most part, an update should consist of a patched build of the
</I>><i> same version of the package released with the distribution, with a few
</I>><i> exceptions:
</I>><i>
</I>><i> * Software versions that are no longer supported upstream with updates
</I>><i> (firefox and thunderbird seem to fall into this category these days)
</I>><i> * Software that is version-bound to an online service (games, virus
</I>><i> scanners?) and will only work with the latest version.
</I>><i> * We will make exceptions for packages that did not make it into mga1
</I>><i> and are additions to the distribution, provided they do not impact any
</I>><i> other packages and can pass full QA.
</I>><i>
</I>><i> Updates are not the appropriate place for packages created to satisfy
</I>><i> certain user's urges for "the latest". These types of builds belong in
</I>><i> backports.
</I>><i> ##########
</I>><i> I read it as "no version bumb is allowed (except for the three
</I>><i> exception-cases listed) - bugs are only fixed using patches", and I
</I>><i> don't see the interpretational freedom to allow upstream's bugfix
</I>><i> releases. Updating from 1.3.2 to 1.3.3 would not be in compliance with
</I>><i> the policy (if not in one of the three exception cases) - this is what
</I>><i> I have called stupid policy (and still do).
</I>><i>
</I>><i> ciao
</I>><i> Christian
</I>><i>
</I>Actually you're right there, currently the only case where a bugfix-only update
would be allowed would be as an exception. And as those should be rare
(hence the term exception) i don't think that's the intent of the third point.
So as some already stated this, as it seems to be allowed to ship bugfix-only
releases as updates, where does the policy state that, and in the case
where it doesn't, shouldn't we extent the policy if that is considered good
practice?
PS: Maybe next time you could improve on your wording, the policy may
currently be incorrect, not reflecting good packaging practices, but as it's
only a policy written by humans, it's not dumb. Just a hint. ;)
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="011336.html">[Mageia-dev] please stop doing "bugs" for updating magia 1
</A></li>
<LI>Next message: <A HREF="011306.html">[Mageia-dev] please stop doing "bugs" for updating magia 1
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#11300">[ date ]</a>
<a href="thread.html#11300">[ thread ]</a>
<a href="subject.html#11300">[ subject ]</a>
<a href="author.html#11300">[ 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>
|
