sm-commit AT lists.ibiblio.org
Subject: Source Mage code commit list
List archive
Re: [SM-Commit] GIT changes to master grimoire by Treeve Jelbert (6c65d4aae051b3d920d610f149afb07ac075bd2d)
- From: "Andraž 'ruskie' Levstik" <ruskie AT mages.ath.cx>
- To: <sm-commit AT lists.ibiblio.org>
- Subject: Re: [SM-Commit] GIT changes to master grimoire by Treeve Jelbert (6c65d4aae051b3d920d610f149afb07ac075bd2d)
- Date: Thu, 14 Dec 2006 11:15:33 +0100
On 9:35:30 2006-12-14 Jaka Kranjc <lynx AT mages.ath.cx> wrote:
> >
> > I've understood that updating to prerelease versions (even in test)
> > isn't preferred. (Although I have to admit I've done it myself
> > sometimes... :))
> >
> > In this case it was probably best to upgrade from rc1 to rc2, but all
> > in all I don't think rc1 should have been there in the first place.
> This was said about critical/important packages iirc.
>
I think it was never defined anywhere... Just a few ppl complained about it.
Personaly I don't mind it in test... but in stable there should only be
stable versions where possible. The one problem there is though that some
developers simply stop developing the old stable version and only work on a
standing development version so in that case it wolud be undesirable to
have the olde outdated stable version... It's basicaly a double-edged
sword...
You either stick with stable only and risk of getting something so out of
date that it doesn't even build/run/do what it's supposed to do or you keep
more or less on the bleeding edge and risk getting something that breaks
without warning. But I look at it this way:
if stable is maintained(i.e. new stable releases) then use that as primary
else use whatever other version is available that is more or less current.
If there's both a stable and development version and both are developed we
can simply provide a choice IF both versions can work with their depends.
And what's the use of having "test" for testing if there's nothing to test
in it... But I agree anything that critical for the system shouldn't be a
development version if possible.
--
Andraž "ruskie" Levstik
Source Mage GNU/Linux Games grimoire guru
Geek/Hacker/Tinker
Hacker FAQ: http://www.plethora.net/%7eseebs/faqs/hacker.html
Be sure brain is in gear before engaging mouth.
Key id = A7A9E461
Key fingerprint = 757E C16B F5B7 DC27 B003 CCED CF95 3A77 A7A9 E461
-
[SM-Commit] GIT changes to master grimoire by Treeve Jelbert (6c65d4aae051b3d920d610f149afb07ac075bd2d),
Treeve Jelbert, 12/13/2006
-
Re: [SM-Commit] GIT changes to master grimoire by Treeve Jelbert (6c65d4aae051b3d920d610f149afb07ac075bd2d),
Juuso Alasuutari, 12/14/2006
-
Re: [SM-Commit] GIT changes to master grimoire by Treeve Jelbert (6c65d4aae051b3d920d610f149afb07ac075bd2d),
Jaka Kranjc, 12/14/2006
- Re: [SM-Commit] GIT changes to master grimoire by Treeve Jelbert (6c65d4aae051b3d920d610f149afb07ac075bd2d), Juuso Alasuutari, 12/14/2006
- Re: [SM-Commit] GIT changes to master grimoire by Treeve Jelbert (6c65d4aae051b3d920d610f149afb07ac075bd2d), Andraž 'ruskie' Levstik, 12/14/2006
-
Re: [SM-Commit] GIT changes to master grimoire by Treeve Jelbert (6c65d4aae051b3d920d610f149afb07ac075bd2d),
Jaka Kranjc, 12/14/2006
-
Re: [SM-Commit] GIT changes to master grimoire by Treeve Jelbert (6c65d4aae051b3d920d610f149afb07ac075bd2d),
Juuso Alasuutari, 12/14/2006
Archive powered by MHonArc 2.6.24.