The smooth running of a Sakai deployment and users' perception of its quality depends on how fast problems are resolved. The sooner you deal with an issue, the quicker it is resolved, and the lesser the disturbance to an end user. Being honest and admitting the fact that there are errors does not imply that Sakai is buggy, just that it is designed from the bottom up to help system administrators to act fast.
Things can go wrong: a piston blown in a car engine, lack of petrol to get you to your destination, or without warning, a hanging office application. I have not interacted with software yet that is perfect. There is no strategy to remove every single defect from a given software product. The primitive computer used for the first lunar landings had as few as 10,000 lines of machine code to control it. The complexity of the task was high, but the number of lines that errors could hide in was low. A modern operating system contains tens of...