When updating an application *that has already been published*, changes made by developers aren't effective immediately, but should instead go through a manual approval mechanism. This will effectively result in two copies of the application in the system, one the currently published one and another with the proposed changes.
When the developer views/edits an application we should show the list of pending changes highlighted (stating that this version isn't yet visible, but pending approval), with an option to see the currently published version instead.
To QA the changes landed for this bug:
1) Create an application, then use the admin interface to make it published,
2) Go back and try editing the application
ER: a new application is created in the Pending status, and differences between it and the published app are displayed on the details (you can see this demo'd at http://people.canonical.com/~michaeln/devportal/devportal-initial-functionality.ogv )
A second version of the app is listed and the the setting is modified, I'm glad to see the status is shown in the admin interface otherwise I think the list would be a drag to look through all the dupes of apps.