Discussion of Sorcery related topics

[Andrew <afrayedknot AT thefrayedknot.armory.com>]

just some random musings:
I like the idea of a test sorcery as a staging area for stable
releases. Also, I think that maybe we should have the concept of a bug
reviewer, someone else on the team that has to review the change and
make sure that the fix works and doesn't break anything, the reviewer
can be choosen at random from other sorcery team members. Then when
the reviewer thinks that the fix is good, doesn't break anything, and
has tested it reasonably, it can be pushed down to the test release.

Also we seem to have this situation where we mark bugs as 'fixed' and
then they sit around waiting to be verified and closed. Maybe we ought to
specify the protocol a little better. Where I work the reporter is the
one to mark the bug as closed when they decide that the bug is actually
fixed to their satisfaction, otherwise they reopen it.

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
> 
> This is just a general layout, but I would like to emphasise that /testing/ 
> is
> important. Also, only the tested fixes should be brought into a bugfix 
> release
> of Sorcery (e.g. 1.7.1 -> 1.7.2) and not the whole devel Sorcery (though I
> believe it was all fixes anyways).
> 
> I'm not sure what's been going on lately, but most people are not happy when
> software labeled "stable" comes fairly broken (especially something as
> essential as the package management).
> 
> We do have a "test" module for Sorcery, perhaps we should use that to 
> release a
> "testing" Sorcery (no relation to test grimoire) as an interim release?
> 
> Thoughts? Comments?
> 
> -sandalle
> 
> -- 
> PGP Key Fingerprint:  FCFF 26A1 BE21 08F4 BB91  FAED 1D7B 7D74 A8EF DD61
> http://search.keyserver.net:11371/pks/lookup?op=get&search=0xA8EFDD61
> 
> -----BEGIN GEEK CODE BLOCK-----
> Version: 3.12
> GCS/E/IT$ d-- s++:+>: a-- C++(+++) BL++++VIS>$ P+(++) L+++ E-(---) W++ N+@ 
> o?
> K? w++++>-- O M-@ V-- PS+(+++) PE(-) Y++(+) PGP++(+) t+() 5++ X(+) R+(++)
> tv(--)b++(+++) DI+@ D++(+++) G>+++ e>+++ h---(++) r++ y+
> ------END GEEK CODE BLOCK------
> 
> Eric Sandall                     |  Source Mage GNU/Linux Developer
> eric AT sandall.us                  |  http://www.sourcemage.org/
> http://eric.sandall.us/          |  SysAdmin @ Inst. Shock Physics @ WSU
> http://counter.li.org/  #196285  |  http://www.shock.wsu.edu/
> 
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
> _______________________________________________
> SM-Sorcery mailing list
> SM-Sorcery AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/sm-sorcery

-- 
________________________________________________________________________
|Andrew D. Stitt                             | astitt AT sourcemage.org    |
|irc: afrayedknot                            | afrayedknot AT t.armory.com |
|aim: thefrayedknot or iteratorplusplus      |                          |
|Grimoire Guru ham/smgl, Porting Team Lead   | ftp://t.armory.com       |
|Author and Maintainer of Prometheus         |                          |
-------------------------------------------------------------------------