I apologize for my sour remark.

Yes, I understand how software release cycles work, I'm a software developer myself building CTI software for hospitals, large corporations and government agencies throughout the Scandinavian market.

This is the third time I've totally broken a website because of this bug. Only today did I find out why. The second time was in the middle of a training session for a partner company on how to design and upload skins.

IMHO, if there's a non-critical bug, provide a patch or let it wait until the next release. But if there's a major packaging error (such as a couple of missing DLL's) in the release, with the potential of being a total show-stopper, I believe the only reasonable approach is to recall the release and fix it as soon as possible.

/ Mats

Add my vote to the "It should have been corrected a long time ago" column.  I think you are right Mats.  There is no good reason to leave it like it is for so long.  Especially since there are so many downloads happening every day, and so many people wasting valuable time when it could easily be corrected.

I can tell you why this is happening though.  There is one and only one person who is actually doing the packaging and publishing of the main downloads. His name is Shaun Walker.
Now someone might come back and say that it isn't true, that there are others that can do it, but the fact is that it is really only that one person doing it. 

---