What do I need to do with the .css files that have appeared in the development environment waiting to be staged after our upgrade?

Environment:

Upgrades from versions November 2012 and older to newer than November 2012

Resolution:

There are new files in the development environment that do not exist in staging as part of the upgrade to a dynamic upgrades release version, and their presence is expected behavior. The expected files should exist in these folders:

/development/views/
/development/views/pages
/assets/themes/basic
/assets/themes/mobile
/assets/themes/standard

You will need to stage and promote the new files as normal to resolve these differences. For additional information regarding the staging and promotion of files in Customer Portal, please refer to Answer ID 2849: Deploying Customer Portal pages

Cause:

The /euf/assets directory is shared between v2 and v3, so during the upgrade any new files, including v3 ones, are copied in. This is a side-effect of upgrading from a pre CP dynamic upgrades release to a post version.