That may be where I go with it. While the common configuration may be convenient in the respect that we can indicate several configurations with one config filter, it is introducing a stigmata in putting packages in production that are throwing warnings. The warnings are not keeping the package from running successfully, but any time I see warnings on a package going into Production, I have issues, harmful to the package or not.
I will likely scale back to single configs, and give MS ideas on how to sculpt Denali to better handle this situation. I don't want to necessarily suppress ALL configuration warnings - some may be legit.
SQL Server Database Administration
Business Intelligence Development