What to do about Infrastructure?

[Thorsten Leemhuis]

Hi!

There yet again was a serious misconfiguration on our one and only
x86-{32,64} builder that was caused indirectly by the branching of
Fedora 14 a week ago. That's the reason why there are some packages with
the tag "fc15" in our rawhide repos, which are still targeting F14, as
we haven't branched yet. It's should be fixed now; thx Nicolas for
letting me know (and partly blame me, as I should have seen that earlier
and checked things when the adjustments for the builder were discussed
something like two weeks ago iirc)

That IMHO is just another(¹) sign that our infrastructure team doesn't
work well (if at all). I don't blame anyone, but we IMHO really need to
do something about it. A full reboot / fresh start with new people seems
way overdue to many.

Are there any options on it? Or maybe anybody even willing to lead that
effort?

Cu
knurd

(¹) there were lots of it in the past years and months (not to branch
when Fedora branches is another(²); that only one of our x86-{32,64}
builders work in another); heck we never even managed to set up a
dependency checker and our server infrastructure to me looks a lot like
fragile hack that could stop to work at any time and might take weeks to
repair

(²) and partly the fault of the "Release Engineering for RPM Fusion",
which basically still is inly me, desperate my announcement from a few
months ago to reduce my contributions to RPM Fusion (or leave it
completely). That needs fixing as well, but doing one step at a time
might be better(³)

(³) to be precise: the whole project and it's (currently close to non
existing) government afaics needs a small restart afaics...