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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] [Freeze] please let in xonotic
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BFreeze%5D%20please%20let%20in%20xonotic&In-Reply-To=%3C201203152035.08429.alien%40rmail.be%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="013119.html">
<LINK REL="Next" HREF="013152.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] [Freeze] please let in xonotic</H1>
<B>Maarten Vanraes</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BFreeze%5D%20please%20let%20in%20xonotic&In-Reply-To=%3C201203152035.08429.alien%40rmail.be%3E"
TITLE="[Mageia-dev] [Freeze] please let in xonotic">alien at rmail.be
</A><BR>
<I>Thu Mar 15 20:35:08 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="013119.html">[Mageia-dev] [Freeze] please let in xonotic
</A></li>
<LI>Next message: <A HREF="013152.html">[Mageia-dev] [Freeze] please let in xonotic
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#13125">[ date ]</a>
<a href="thread.html#13125">[ thread ]</a>
<a href="subject.html#13125">[ subject ]</a>
<a href="author.html#13125">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Op donderdag 15 maart 2012 18:35:04 schreef Juan Luis Baptiste:
><i> On Thu, Mar 15, 2012 at 12:24 PM, Bertaux Xavier <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">bertauxx at yahoo.fr</A>> wrote:
</I>><i> >> If this is the case, then I say that xonotic should be allowed to be
</I>><i> >> updated.
</I>><i> >
</I>><i> > I'm not about to be okay with that, a version Freeze only accepts
</I>><i> > updates on bug fixes and security warnings, so RC to Release is OK but
</I>><i> > not to revision's change, otherwise that would mean that if fate xonotic
</I>><i> > in version 0.7 just before the Release we should built.
</I>><i> > To me this should be pushed Backport, to limit the update after Release
</I>><i>
</I>><i> Backports are for new versions, not bug fixes. In this case even as
</I>><i> this is a new version, the use of an older version of the game client
</I>><i> with a new game server version could bring issues to users, so that
</I>><i> makes this release more of a "bug fix release", because we are trying
</I>><i> to avoid any possible problem to our users, not because we want to
</I>><i> have the latest version of the game. If we leave the current version
</I>><i> and then a user reports a problem while playing the game, the 0.6 or
</I>><i> 0.7 or whatever version is available at the time would be pushed as an
</I>><i> update, not as a backport.
</I>
well, the version policy is for updates.
my point here is that we should maybe equalize & simplify our policys by
having the same kind of "exceptions" in both policies.
of course, there may be a good reason to now similar exceptions to both
policies, it's just that atm, i don't see any.
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="013119.html">[Mageia-dev] [Freeze] please let in xonotic
</A></li>
<LI>Next message: <A HREF="013152.html">[Mageia-dev] [Freeze] please let in xonotic
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#13125">[ date ]</a>
<a href="thread.html#13125">[ thread ]</a>
<a href="subject.html#13125">[ subject ]</a>
<a href="author.html#13125">[ 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>
|
