Alternatively Arnim, you can consider standard software development common sense which states that you don't publish a major new software release then disappear from the face of the Earth for 2 weeks.

Even assuming this is acceptable, it's apparent from the mailing list and posting here that there are one or two people still working within maemo.org, and the lack of any communication from more senior management tells me that there is no effective escalation process in place for when major problems do occur.

From the outside, maemo.org appears to be a noddy operation and it doesn't come close to a professionally run software development outfit. Their process is a confused mess and multiple promises have been made for far longer than I can remember that the situation will improve, yet there is no sign of this happening - where's the changelog for each release? That should be easy to produce, assuming the defects were tracked properly.