This would mean that the outsystems Platform Servers would be fully aware of each other's state and the E-spaces and extensions that have been set-up on the server.

I think this would be a good aid in seeing whether a version is taking too long to be deployed in a live environment.

Think of a situation where the status of an E-space that is in Q&A could change to "Approved to go Live" by a tester / user.
This gives green light for the Application Manager to rollout the version.

+ upon eSpace publication allow the ability to comment on changes made to an eSpace application. (similar to how it works with subversion commit).

So..
You would need to be able to set up the development, test, acceptance and production environment (test & acceptance should be able to be combined) Systems managent can then do easy cross server deploys by selecting an eSpace and set it to the next level. After selection the deployment tool should list all needed eSpaces and Extensions used by the eSpace and show checkmark which has to be deployed also. After check systems management can then deploy all to the next server.

This should then also include that users can enter a user defined version number. This version number can then be used to identify the eSpace versions accross servers. eSpaces are only transferrable when assigned a user defined version number. Default it should start with number like 1.0.

eSpace version description/comment is a must: when you have hundreds of eSpace versions and a lot of change requests it's dificult to keep track of what went live and when.

Reminder for the Dutch Bits & Bijt session, One Wish to rule them all! ;-)

Thanks for the great response for our Change Center project! 

See you all at the Next Bits & Bijt!

Kind regards,

Matthias Preuter

Welcome to LifeTime!

Finally we are using this great product @Oxxio

mission accomplished ;-)