Public SourceMage Discussion List

[Hamish Greig <hgreig AT bigpond.net.au>]

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

On Fri, 11 Jul 2003 10:23, Sergey A. Lipnevich wrote:
> devel/test/stable grimoires doesn't solve this? Maybe instead of pushing
> from devel to test every week or two, we have to establish some kind of
> a "signal" in a spell as to whether it's ready to go into test/stable?
> And that wouldn't be just a section guru's call, but something like
> "three successful" installs. If sorcery would send back (non-private)
> information that such and such spell has just succeeded installing (or
> group such messages into packages to send all of it at once), our
> "back-end" would push the spell into test after three successful reports?
This i really like, we need feed back from end users and we need more merging 
into test and stable. The main reason i actually started to use devel is 
because stable is so far behind on KDE. KDE 3.1.2 has been out for 2 months 
now and apart from an issue with compiling kdemultimedia it has been rock 
solid(stable). But stable doesn't have it yet.
On the issue of sending success results then three attempts might not be 
enough considering the dependancies some spells have, if an update (rather 
than install) was done and spell A was broken by spell B (but both where 
already installed so dependancies weren't ordered) we wouldn't find that out 
until someone eventually did a rebuild. Which potentially puts timebombs in 
test and stable...
A (bad?) example is t1lib which is now (again) at a stable 1.3 release. there 
is a *buggy* 5.0.0 release available from "someone's" site that has either a 
major API change or is just buggy. any way the problem was that only half a 
dozen things depend on t1lib so this faulty update went unnoticed for THREE 
months until i tried to update science section this week.  
Having tinderboxes dedicated to rebuilding the grimoire with an update 
between 
each rebuild would help this but i don't have the hardware to dedicate for 
this (unfortunately). 
I think some thought must go into our merging and release schedule/ policy. 
Stable can be stable with regular updates and many of the bugs we catch in 
devel should be caught in test...
If both test and stable were in fact more uptodate more people would use them 
leaving devel as a place were if you do an update it is assumed you  atleast 
do cast --fix AND/OR sorcery --rebuild so critical bugs are knocked out 
before they are merged into test. ATM i think many people are using devel 
just for the new releases with-out a thought for compatibility with other 
installed software. Once again tinderboxes are critical to this...
bah I ramble too much!
Hamish
- -- 
Do You SMuGL!?
# Linux so advanced it may as well be magic!
# http://www.sourcemage.org/
# A onestop guide to Defenestration!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/DiWD8fSufZR6424RAmT7AJ9Yt9uGzdfsKQMyM83+/dvDrN1HEgCcCuse
0qRLaTNXkAyuRex4zyBUrmA=
=Olj/
-----END PGP SIGNATURE-----