[
http://mifosforge.jira.com/browse/MIFOS-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Singh updated MIFOS-4222:
-------------------------------
Description:
Delete NSDU code from the mifos codebase, do not archive it as it would be
accessible from source control via history and old branches. Do not delete NSDU
tables as they would represent the history for any deployment, useful for
diagnostic purpose.
Change deployment and build scripts to run the new scripts from using
Liquibase. Note that it is different from our current approach where we do not
run upgrade scripts during development. This should be run before the test data
is setup. The deployment script should have modes for running expansion or
contraction or both during deployment.
Delete old NSDU scripts written for this release.
The application version should be maintained in properties/config files. Two
numbers need to be maintained. The highest value of expansion and contraction
script individually. Implement version check which ensures that application
version is same as database version for both these numbers.
was:
Delete NSDU code from the mifos codebase, do not archive it as it would be
accessible from source control for older branches. Do not delete NSDU tables as
they would represent the history for any deployment, useful for diagnostic
purpose.
Change deployment and build scripts to run the new scripts from dbdeploy.
During development both expansion and contraction mode should be used one after
other. Note that it is different from our current approach where we do not run
upgrade scripts during development. This should be run before the test data is
setup. The deployment script should have modes for running expansion or
contraction or both during deployment.
Delete old NSDU scripts written for this release.
The application version should be maintained in properties/config files. Two
numbers need to be maintained. The highest value of expansion and contraction
script individually. Implement version check which ensures that application
version is same as database version for both these numbers.
> [Tech] Migrate to the new approach of database upgrade
> ------------------------------------------------------
>
> Key: MIFOS-4222
> URL: http://mifosforge.jira.com/browse/MIFOS-4222
> Project: mifos
> Issue Type: Story
> Components: Database
> Affects Versions: Elsie F - Iteration 6
> Reporter: Vivek Singh
> Assignee: Tejus Datta
> Priority: Major
>
> Delete NSDU code from the mifos codebase, do not archive it as it would be
> accessible from source control via history and old branches. Do not delete
> NSDU tables as they would represent the history for any deployment, useful
> for diagnostic purpose.
> Change deployment and build scripts to run the new scripts from using
> Liquibase. Note that it is different from our current approach where we do
> not run upgrade scripts during development. This should be run before the
> test data is setup. The deployment script should have modes for running
> expansion or contraction or both during deployment.
> Delete old NSDU scripts written for this release.
> The application version should be maintained in properties/config files. Two
> numbers need to be maintained. The highest value of expansion and contraction
> script individually. Implement version check which ensures that application
> version is same as database version for both these numbers.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://mifosforge.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
What happens now with your Lotus Notes apps - do you make another costly
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
