Sorry, that's my job

I don't exactly recall what you mean by 'not built for a month' - we had some down time with the ARMv7 build but all the due while we were doing ARMv5 images. We uncovered a GCC bug that broke even the simplest of things, including DBus and it took some time to locate and fix.

If you're speaking of the problem that we had two weekly releases not getting built properly, well, that was due to a release procedure not getting communicated properly when our release guy was on vacation. We're now part of the meego.com release machinery, we weren't before and that solves that problem once and for all.

I vote that you go and look at developer mailing list, meego-releases, the handset reports, bugs.meego.com, metrics and our IRC channel logs for #meego-arm to see there's real work going into it.

Even if MeeGo 1.1 isn't the swan I hoped myself it would be, I'm bloody proud of the work and effort we've (as in the team and the people contributing to the port) put into the N900 side of things.

And it'll only get better.

We're making sure we can keep the N900 port alive for a -long- time.