Maverick toolchain

[Mark Shuttleworth]

On the kernel front, we are in a post-LTS release and still early enough
to identify and address kernel issues. I think it's a valuable lesson to
remember for future reference that toolchain discussions should engage
the kernel team, but I don't see the need to derail the train because of
an objection raised now. We can use the kgcc plan, or we could simply go
with the Linaro toolchain for kernel and do the kgcc work if it becomes
clear that it's needed. The balance of probabilities is that the work is
not needed at all.

On 20/07/10 20:45, Matthias Klose wrote:
> Another concern raised is the amount of rebuilds which may hit the
> archive for the rebuild of package to make use of the new arm
> optimizations.  According to James T.  a rebuild of all packages found
> on the CD images would be fine, and maybe as well a rebuild of main if
> this is stretched over some time.

I understand there's a quality risk (new build, new issues) but your
analysis seemed to suggest that would be minimal and quickly addressed.
There's also a timing / resource risk, and we'll gladly allocate more
hardware to the build farm for a rebuild if that's material.

Robbie, the agreement was we'd make a decision based on the rebuild test
and analysis, and we could hardly have asked for more favourable
findings, are you willing to unpause the process, especially if we
follow Doko's recommendations?

Mark