Skip to Content.
Sympa Menu

sm-commit - Re: [SM-Commit] GIT changes to master grimoire by David Brown (cbf44b0470307541f2218c852717a8695570630d)

sm-commit AT lists.ibiblio.org

Subject: Source Mage code commit list

List archive

Chronological Thread  
  • From: Andrew Stitt <afrayedknot AT thefrayedknot.armory.com>
  • To: sm-commit AT lists.ibiblio.org
  • Subject: Re: [SM-Commit] GIT changes to master grimoire by David Brown (cbf44b0470307541f2218c852717a8695570630d)
  • Date: Tue, 31 Oct 2006 20:03:41 -0800

On Wed, Nov 01, 2006 at 07:37:27AM +0400, George Sherwood wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Tue, 31 Oct 2006 20:11:40 -0700
> "David Brown" <dmlb2000 AT gmail.com> wrote:
>
> > > And where did this come to be? Guess it is just another one of
> > > those unwritten rules. Is there anything that is broke? Or are we
> > > just going to test and never update like so many other things in
> > > this distro? I have just about had it.

Please calm down and please do not take this personally.

> >
> > No the sorcery team does have plans to update but we need to be
> > notified about these things. Sorcery is wrtten in bash we need to be
> > given the opportunity to test it so we don't mess up other peoples
> > computers. Andrew will allaborate on this further since (I hope) he's
> > going to do the testing to make sure it works.
> >
>
> Fine, if that is the procedure let it be so. I did the update to bash
> 3.1 and never heard of this. I added all the patches to bash 3.1 and
> never heard of this.

Actually I did tell you to give me a heads up last time w/ 3.1. And for
the 3.0 there was considerable collaboration between the grimoire team
and sorcery team on when the update would go through. Both leads signed
off before it happened. I figured that the 3.1 case was an oversight
and that next time we'd get some sort of testing time or notification
that an update was planned.

Furthermore, both the 3.0 and 3.1 updates required non-trivial
changes to sorcery. So theres no reason to think that 3.2 would be any
different, even if there aren't any known problems.

Simple basic testing has proven insufficient in the past. Sorcery is
written in bash, and its my job to ensure that its stable so you can do
your grimoire updates. Please help me do my job and in the future provide
some sort of heads up next time.

I was actually planning on giving a go-ahead to update bash. I am on the
bash-bugs mailing list and have been following along. I was waiting for
things to settle down first.

> I test 3.2 although in a ordinary does it work
> method, found one thing that didn't work waited for patch one that
> fixed it and test some more with many casts and sorcery commands and it
> worked. But no one asked me anything about that.
>
> Like so many things in this distro unwritten and always changing.
> Extremely frustrating to work. I am ready to let Treeve do all the
> grunt updates. I will just sit back update my grimoire and see how it
> goes.

Yes, we are short on workers, lets not take this out on each
other. Reverting the change wasnt meant to be personal. Its practical.

As far as unwritten things go, well, Im doing the best I can to fix the
docs situation with the RDP team...

Perhaps take a timeout from routine spell updates and work on the other
nagging broken stuff.

We can talk about this more, perhaps on irc.

-Andrew






Archive powered by MHonArc 2.6.24.

Top of Page