From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2012-March/013152.html | 101 ++++++++++++++++++++++++++++++ 1 file changed, 101 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-March/013152.html (limited to 'zarb-ml/mageia-dev/2012-March/013152.html') diff --git a/zarb-ml/mageia-dev/2012-March/013152.html b/zarb-ml/mageia-dev/2012-March/013152.html new file mode 100644 index 000000000..d0011719a --- /dev/null +++ b/zarb-ml/mageia-dev/2012-March/013152.html @@ -0,0 +1,101 @@ + + + + [Mageia-dev] [Freeze] please let in xonotic + + + + + + + + + +

[Mageia-dev] [Freeze] please let in xonotic

+ Samuel Verschelde + stormi at laposte.net +
+ Fri Mar 16 08:57:45 CET 2012 +

+
+ +
Le jeudi 15 mars 2012 20:35:08, Maarten Vanraes a écrit :
+> Op donderdag 15 maart 2012 18:35:04 schreef Juan Luis Baptiste:
+> > On Thu, Mar 15, 2012 at 12:24 PM, Bertaux Xavier <bertauxx at yahoo.fr> 
+wrote:
+> > >> If this is the case, then I say that xonotic should be allowed to be
+> > >> updated.
+> > > 
+> > > I'm not about to be okay with that, a version Freeze only accepts
+> > > updates on bug fixes and security warnings, so RC to Release is OK but
+> > > not to revision's change, otherwise that would mean that if fate
+> > > xonotic in version 0.7 just before the Release we should built.
+> > > To me this should be pushed Backport, to limit the update after Release
+> > 
+> > Backports are for new versions, not bug fixes. In this case even as
+> > this is a new version, the use of an older version of the game client
+> > with a new game server version could bring issues to users, so that
+> > makes this release more of a "bug fix release", because we are trying
+> > to avoid any possible problem to our users, not because we want to
+> > have the latest version of the game. If we leave the current version
+> > and then a user reports a problem while playing the game, the 0.6 or
+> > 0.7 or whatever version is available at the time would be pushed as an
+> > update, not as a backport.
+> 
+> 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.
+> 
+
+It's already the case. If you re-read Ennael's mail about version freeze, it 
+says exactly that about exceptions.
+
+Samuel
+
+ + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1