Skip to Content.
Sympa Menu

sm-grimoire - Re: [SM-Grimoire] Work in progress spells

sm-grimoire AT lists.ibiblio.org

Subject: Discussion of Spells and Grimoire items

List archive

Chronological Thread  
  • From: Hamish Greig <hgreig AT bigpond.net.au>
  • To: Grimoire <sm-grimoire AT lists.ibiblio.org>
  • Subject: Re: [SM-Grimoire] Work in progress spells
  • Date: Mon, 13 Oct 2003 13:03:55 +1000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 13 Oct 2003 04:22, Ladislav Hagara wrote:
> > I was hoping it would allow easier integration and a WIP (if that be the
> > name
>
> I think WIP does not help us.
> For WIP spells we have devel nongrimoire. Spells in test grimoire are not
> WIP they are adjusted for the test grimoire.
> We only must ensure interdependent spells are integrated from test to
> stable at the same time.
> Before integration to stable all changes should be tested, prometheus can
> help.
>
> - lace -
>
Try not to focus on the WIP name, this is valid for all sections/ spells I
think. The name of the file could be NON_INTEG or STAY it doesn't matter.
The point about devel non-grimoire is valid too, but we need to extend our
focus.
True works in progress get rewritten in devel were they won't hose users
machine, true. Once ready a spell then goes into test. THat doesn't mean that
spell is 100 % bug free, it just means it is ready for user testing.
If user testing finds some bugs that can't be immediately (high
possibility)fixed then to stop this buggy version going into stable it would
have a STAY (or whatever) file so it won't go into stable and the old version
remains usable.
This is also true for simple version updates. A version update might cast
fine
but cause 50% of spells that depend on it to fail (like orbitcpp, whose
integration into stable was my fault, i know). If the guru decides not to
downgrade the version because he is working on fixing the problem (or the
author is fixing it) then that is acceptable. But to stop it from being
integrated into stable it needs a STAY file.
Test is were bugs get fixed now so we need a foolproof method to stop bugs
from getting integrated into stable.
The way things are currently, a user who can't cast a spell in test due to a
bug should be able to scribe add stable , scribe swap stable test and then
cast the stable version.
Stable *is* a fallback for test isn't it ?
Hamish

- --
IRC nick: drmoriarty
SMGL co-conspirator
#Do You SMGL!?
# Linux so advanced it may as well be magic!
# http://www.sourcemage.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/ihYb8fSufZR6424RAoYsAJwJf5cRT/T+xt0ZttVDRq/LwPOFkwCdHfbX
/J81yMz3RNaMFxkO8pwdhEk=
=ShWN
-----END PGP SIGNATURE-----





Archive powered by MHonArc 2.6.24.

Top of Page