moonbase.tar.bz2 versus darksideofthemoon.tar.bz2

[Auke Kok]

On 05/25/2011 04:52 AM, samuel wrote:
> Hi fellow devs,
>
> After 2 breakages this week (mesa-lib and udev) I'm a bit sick of it.
> It was once our intention that the developer that bumps stuff needs to
> test it too. Clearly this ain't working like we would like it to work.
> Right now I'm even considering moving some 'production' machines away
> from lunar just to avoid these breakages. As I'm a developer of lunar
> that would pretty much feel like giving up lunar completely.
> So I'd like to start implementing a "stable" moonbase and a "edgy"
> moonbase (names to be discussed). The "stable" moonbase would include
> only updates that are verified by several key developers, at least for
> core componentes like udev, ssh, openssl, pam, etc etc... (I would
> love to think out some automated build system to test this for us)

should be fairly trivial to setup a build root and test each update to 
moonbase. the question is whether we have the infrastructure for that 
(answer: probably not).

Besides that, the only way to have a 2-staged moonbase is to have some 
form of "promotion" in place that is based on QA. Automated testing 
would pretty much be the only way to guarantee that promotion is done 
sanely,

On top of that, remember that if you patch X, your test case includes 
recompiling every package that compiles against X. The resource usage is 
potentially huge: some changes could affect all of moonbase.

> Right now multiple devs are no longer running updated moonbases on
> their own boxes because they are scared their boxes might break...
> Seems like a *bad* situation to me
>
> If no one objects i'd like to start implementing this (preferably yesterday...)
>
> If anyone has a good idea on how to implement this, please speak free.

heh, you'll need:

lots and lots of time
lots and lots of build resources

Auke