[
http://mifosforge.jira.com/browse/MIFOSADMIN-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Whitney updated MIFOSADMIN-205:
------------------------------------
Fix Version/s: (was: Cloud Release A - Iteration 4)
Cloud Release A - Iteration 5
Cloud Release A
> Clone and test upgrade with SECDEP data
> ---------------------------------------
>
> Key: MIFOSADMIN-205
> URL: http://mifosforge.jira.com/browse/MIFOSADMIN-205
> Project: mifos administration
> Issue Type: Story
> Components: Cloud Instances
> Reporter: Ryan Whitney
> Assignee: Sumit Shah
> Fix For: Cloud Release A, Cloud Release A - Iteration 5
>
>
> Before beginning our upgrade, we want to test the upgrade process on a
> customer.
> We'll use SECDEP since we need to do some other testing for them on reports.
> STeps would include
> 1. Clone production system = give it a dns name of "upgrade-test.mifos.org"
> 2. Upgrade to Mifos 2.0
> 3. REview and test instance (Assign to Ryan for this)
--
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
------------------------------------------------------------------------------
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world?
http://p.sf.net/sfu/oracle-sfdevnlfb
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
