In order to avoid problems with releases a release validation process should be created. The following problems were encountered in the past and should be checked by this release process:

• incorrect XSD (ISPN-934)
• upload problems to SF (e.g. today the release script silently failed to upload the binaries to SF as they changed their certificate)
• wrong binaries being deployed under the "right" name(e.g. a 4.x release was performed from trunk and not from the 4.2.x branch)

Any others?

All these cause a lot of community frustration and time to debug and fix.

These can potentially be automated.