[
http://mifosforge.jira.com/browse/MIFOS-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Monsen updated MIFOS-4471:
-------------------------------
Description:
The database upgrade mechanism (aka "non-sequential database upgrades")
supports automatically upgrading the Mifos database when the Mifos application
(the war) is upgraded.
We need to periodically flatten (collapse) upgrades from time to time,
depending on how many releases back we are supporting. Culling old code is
essential to keeping our code maintainable.
Since the recent 2.0.0 release, we are ready to [remove the question group
migration
code|http://thread.gmane.org/gmane.comp.finance.mifos.devel/10713/focus=10717],
and we (in today's standup call) also decided that in order to upgrade to Elsie
F, one would be required to be on at least Mifos 2.0.0.
Therefore, in head/master, we should flatten all database upgrades prior to
mifos-v2.0.0-schema.
Removing the question group migration code is covered in [a different
issue|MIFOS-4472].
was:
The database upgrade mechanism (aka "non-sequential database upgrades")
supports automatically upgrading the Mifos database when the Mifos application
(the war) is upgraded.
We need to periodically flatten (collapse) upgrades from time to time,
depending on how many releases back we are supporting. Culling old code is
essential to keeping our code maintainable.
Since the recent 2.0.0 release, we are ready to [remove the question group
migration
code|http://thread.gmane.org/gmane.comp.finance.mifos.devel/10713/focus=10717],
and we (in today's standup call) also decided that in order to upgrade to Elsie
F, one would be required to be on at least Mifos 2.0.0.
Therefore, in head/master, we should flatten all database upgrades prior to
mifos-v2.0.0-schema.
Removing the question group migration code is covered in a different issue.
> move forward latest database checkpoint
> ---------------------------------------
>
> Key: MIFOS-4471
> URL: http://mifosforge.jira.com/browse/MIFOS-4471
> Project: mifos
> Issue Type: Task
> Components: Database
> Reporter: Adam Monsen
> Priority: Major
>
> The database upgrade mechanism (aka "non-sequential database upgrades")
> supports automatically upgrading the Mifos database when the Mifos
> application (the war) is upgraded.
> We need to periodically flatten (collapse) upgrades from time to time,
> depending on how many releases back we are supporting. Culling old code is
> essential to keeping our code maintainable.
> Since the recent 2.0.0 release, we are ready to [remove the question group
> migration
> code|http://thread.gmane.org/gmane.comp.finance.mifos.devel/10713/focus=10717],
> and we (in today's standup call) also decided that in order to upgrade to
> Elsie F, one would be required to be on at least Mifos 2.0.0.
> Therefore, in head/master, we should flatten all database upgrades prior to
> mifos-v2.0.0-schema.
> Removing the question group migration code is covered in [a different
> issue|MIFOS-4472].
--
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
------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
