alpha vs beta -- why we don't go updating build toolchains mid-beta

Guys.. we're now in a very ugly little spot due to the recent GLIBC 
update in devel.  All of our ISOs are being
built from devel at the moment, which means we're getting UNSTABLE 
packages released as 'stable' ones, and
which end up having dependency issues when the 'stable' (Dockyard) tree 
has older packages.

Even if that weren't the case, we simply can't continue to do things the 
way we did for alpha.. i.e. casually
building new versions of gcc / binutils/ glibc in the devel tree.  At 
this stage in the game, we're supposed to
ONLY be >>FIXING<< core packages like KDE, glibc, gcc, binutils, and the 
kernel.  If our core os
packages keep changing, then this is never going to be a truly 'stable' 
OS in any sense of the word, except
maybe the one that says it doesn't crash.

it doesn't matter if things seem to run fine with the new packagse on 
your machine.  That's entirely beside the point.
Right now the point is stability and variable elimination.  If the core 
packages don't change, then we can rule out
a change as being the cause of an ongoing problem.  If we identify one 
of the core packages as being part of a
problem, then we fix whatever's wrong with taht one package.  Otherwise 
we just keep causing more work for
ourselves.

It's time we  isolate dockyard and dockyard-devel as the 'rc' trees we 
plan to use for a 'gold' release, and create
a new 'unstable' or whatever you want to call it, tree for post-gold 
purposes.