Discussion of Sorcery related topics

[Eric Schabell <eschabell AT sourcemage.org>]

On Tue, Jan 27, 2004 at 06:27:15PM -0800, Eric Sandall wrote:
> Due to some of the problems with stable Sorcery lately, I would like to 
> propose
> that the Sorcery Team implement some type of verification process for 
> releasing
> a stable version. Below I will provide my suggested template, but this is 
> just
> to get the ball rolling, no need to follow it exactly (and I'm being 
> pedantic,
> so don't take offense at the verbosity). ;)
> 
> 1. Fix one bug on your local copy of Sorcery devel
> 2. Test that one bug to the full extent that the report specifies
> 3. Submit your fix for that bug to Sorcery devel
> 4. Integrate that fix /only/ to Sorcery stable
> 5. Repeat #2 as well as testing anything which is related to the bug
> 6. Submit the fix to Sorcery stable
> 7. Release a new version of Sorcery stable if the fix is major enough (such 
> as
> it breaks machines, Sorcery is not usable, etc., but things such as "xterm
> title doesn't change" are okay to leave for a bit, though they shouldn't be
> there in the first place ;)).
> 8. Announce new version
> 9. Repeat 1-9
> 
Sounds good to me, where do I get testers, users that report on fixed
bugs back into bugzilla, time, extra hands? ;-)

Same shit, different day. I am pretty much alone on sorcery right now...
occasional help from the sidelines from rycee and dufflebunk, but that
is it.

Patience is all I can ask for.

erics