Some things that come to mind... fix dependency generation so that ant scripts always match distributed jars.
automate sample testing wrap up some of the scripts that we have been using from the release wiki page [1] into something we can run against the release be better at using a checklist to ensure coverage of the various combinations that we now have to cover (not sure what this means other than having a better release report on the wiki) separate released modules from non released modules in the trunk so we don't have to go through the dance of deciding what is in the release each time What else? Simon [1] http://cwiki.apache.org/confluence/display/TUSCANY/Making+releases
