If you have some minutes left, pleas vote the following items on Connect for SSIS features missing in SQL Server Denali:

• Filter SSIS events: It is currently not possible to choose the events that need to be logged within the SSIS database. Instead everything is logged by default which can create a lot of traffic and data amount. https://connect.microsoft.com/SQLServer/feedback/details/658674/filtering-ssis-logging-events-in-denali-ssis-server
• Non transparent package deployment: The new SSIS database has the possibility of tracking project versions to be able to role back to a certain version. Currently there is no chance to enter a description of what has been changed in a new deployment. This leads to non transparent versions and when you want to role back you don’t know to which version because you have no version documentation. Ideally it would be great if a list of packages, that have been changed in a certain project version, can be shown for a certain project version. https://connect.microsoft.com/SQLServer/feedback/details/678363/denali-ssis-deployment-describe-deployment-changes
• Introduction of Project Version numbers: Currently there is no relationship of a Integration Services project tracked in Team Foundation Server for development purposes and SSIS project versions which have been deployed tracked by the SSIS database. A really helpful feature would be to introduce SSIS project version numbers, like in a C# project. These project numbers can then be stored for every SSIS project version in the SSIS database so that you know which SSIS Code Version within TFS maps to your deployed project version on the SSIS Server. https://connect.microsoft.com/SQLServer/feedback/details/678364/denali-use-ssis-version-numbers-within-the-project-and-the-server-versions
• Possibility to choose packages for deployment: In the current CTP it is only possible to deploy the whole project with every SSIS package included whether they have been changed or not. I know a lot of customer scenarios where customer only want things to be deployed which have been changed! Deploying always everything can be a real pain. https://connect.microsoft.com/SQLServer/feedback/details/678362/choose-of-ssis-package-to-be-included-in-denali-deployment-package
• Possibility to assign more the one environment for package execution: Before Denali it was possible to assign to a SSIS package more then one configuration. This offered developers the possibility to separate configurations for example general configuration settings, which more then 1 package needed (like connection strings), and package specific configurations, like transaction handling. Now in Denali I can only assign one environment to one package execution which means that I have to create for every package an environment and have to mix project specific settings and package specific settings. If I want to change now a connection string configuration, which is used in 20 packages, I have to change 20 environments. https://connect.microsoft.com/SQLServer/feedback/details/679409/denali-ssis-possibility-of-multiple-environment-configurations-per-package-execution-not-povided