[
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. Some parts of NSDU code might be required for dbunit work.
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.
Change the dbunit code to work using liquibase.
Delete old NSDU scripts written for this release.
was:
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.
> [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. Some parts of NSDU code might be required for dbunit
> work.
> 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.
> Change the dbunit code to work using liquibase.
> Delete old NSDU scripts written for this release.
--
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
------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d
_______________________________________________
Mifos-issues mailing list
Mifos-issues@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mifos-issues
