On Wed, 2010-12-01 at 23:20 +0100, Henrik Nordström wrote:
ons 2010-12-01 klockan 14:37 -0500 skrev omalleys(a)msu.edu:
> I was looking at today. Today the project has a handful of builders.
> How does the project get on track to appear to be a viable solution,
> rather then a secondary arch that is 2 releases behind to someone
> unfamiliar with the project? What is the easiest way to get there
First step is to massage the builders until F13, F14 and finally rawhide
can be shadowed automatically and we can focus on actual arm issues more
than stupid build issues.
This is doing very good progress, and should from what I understand
settle in a couple months. At the moment the build farm is working hard
on catching up.
That's how I'd categorize the current state of things too.
In terms of hardware: At the moment we have 17 active builders, which
are armv5 512M machines. There are also a few others that are currently
being used for testing and will be inserted back into the build farm
soon; the full hardware list is 21 GuruPlugs, 1 OpenRD, 1 SheevaPlug, 1
BB-C4, and 1 BB-xM.
There are also 15 PandaBoards on order, which should at least double the
farm capacity because they should outperform the plugs (dual core, 1GB);
if DigiKey's ship dates are to be believed, we're looking at having
these online in early January.
The main issue isn't so much build capacity as the manual chore of
clearing up build failures. Most of this work is being done daily by
Paul Whalen, and he's had some great help on key packages by Rick Mattes
and others. That's definitely the place to put additional energy if
we're going to accelerate things.