[
http://mifosforge.jira.com/browse/MIFOS-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Singh updated MIFOS-4220:
-------------------------------
Description:
For older releases we would continue to use NSDU. The migration should take
care of scripts for current release only.
Tasks
- categorize scripts into contraction and expansion. [This was not mentioned in
the epic. The expansion scripts should also take care of keeping the data in
case an undo would be performed]
- write them in Liquibase
- convert any code based migration to sql based
- create maven script for running Liquibase from command line, not called from
any CI or Dev build targets yet. This should be done in a way that expansion,
contraction or both can be run conveniently.
(Do not delete old scripts and keep the new scripts in a folder where NSDU
doesn't see it. This is an interim step.)
was:
For older releases we would continue to use NSDU. The migration should take
care of:
- categorizing scripts into contraction and expansion
- converting any code based migration to sql based
(Do not delete old scripts and keep the new scripts in a folder where NSDU
doesn't see it. This is an interim step.)
Create maven script for running this from command line, not called from any CI
or Dev build targets yet.
> [Tech] Migrate the scripts for current release (only) to liquibase
> ------------------------------------------------------------------
>
> Key: MIFOS-4220
> URL: http://mifosforge.jira.com/browse/MIFOS-4220
> Project: mifos
> Issue Type: Story
> Components: Database
> Affects Versions: Elsie F - Iteration 6
> Reporter: Vivek Singh
> Assignee: Tejus Datta
> Priority: Major
>
> For older releases we would continue to use NSDU. The migration should take
> care of scripts for current release only.
> Tasks
> - categorize scripts into contraction and expansion. [This was not mentioned
> in the epic. The expansion scripts should also take care of keeping the data
> in case an undo would be performed]
> - write them in Liquibase
> - convert any code based migration to sql based
> - create maven script for running Liquibase from command line, not called
> from any CI or Dev build targets yet. This should be done in a way that
> expansion, contraction or both can be run conveniently.
> (Do not delete old scripts and keep the new scripts in a folder where NSDU
> doesn't see it. This is an interim step.)
--
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
