Hi Roberto, > normally every change in production should be part of a change log > process and require approval, so an automatic upgarde can break this > rule that is quite a "da facto standard" in production (not only for > tha database, but for everityng is necessary to change)
Giving administrators the ability to run upgrades outside of the main Mifos application (and probably with more fine grained control) is something that we will want to do. When we do that, we should be able to make use of the same mechanism that is currently being used for the automated upgrades. We could probably do something along these lines without too much work as another ant build target (although you can imagine more elaborate user interfaces too). Aside from the production environment, the automated upgrades are very convenient for developer, demonstration and test deployments where moving quickly and easily from one database version to the next is very useful and time saving. --Van ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
