See VERSIONING (https://github.com/openMF/mifosx/blob/master/VERSIONING.md) for information on what updates to the version number implies for the platform.
- 09 May 2013 - 1.1.0.RELEASE
- 08 May 2013 - 1.0.1.RELEASE
- 07 May 2013 - 1.0.0.RELEASE
- 30 April 2013 - 0.12.1.beta
- 30 April 2013 - 0.11.4.beta
- 22 April 2013 - 0.12.0.beta
- 17 April 2013 - 0.11.3.beta
- 10 April 2013 - 0.11.2.beta
- 05 April 2013 - 0.11.1.beta
- 05 April 2013 - 0.11.0.beta
Feature Release
Scope of release:
General improvements to display of audit details, pagination of list apis. New api to list loans/loan applications.
In addition to items mentioned below see 1.1.0.RELEASE on JIRA: https://mifosforge.jira.com/browse/MIFOSX/fixforversion/11932 for full details of issues addressed in release.
Core Issues:
- [MIFOSX-334] - Group loses clients when updating
- [MIFOSX-226] - Add ability to API to list loans for applications that require loan centric view of data
- [MIFOSX-339] - Allow retrieving of all items on paginated endpoints
Bug Release
- MIFOSX-343 - When viewing Audit details, integer values (rather than string values) for officeId and clientId cause exception
The first community sanctioned public release of new mifos platform project ('Mifos X').
Scope of release:
In addition to items mentioned below see 1.0.0.RELEASE on JIRA: https://mifosforge.jira.com/browse/MIFOSX/fixforversion/11833 for full details of issues addressed in release.
Operational Functionality:
- Client Loan Portfolio Management
- Cash-based Accounting
- Audit of all changes
- Reporting (about 30 Reports)
- Comprehensive and flexible ability to configure (on request) MFI specific additional client and loan data.
Organisational Functionality:
- Currency, Funds, Offices, Staff/Loan Officers
- Loan Products
- support for declining balance or flat interest methods
- Ability to configure mfi customised repayment processing
- Charges
- Fees & Penalties
User Admin Functionality:
- Users, Roles, Permissions
- 4-eye principle / Maker-Checker
Bug Release
- MIFOSX-311 - Zero % loan products or loan applications are not allowed due to validation checks
Back ported bug fixes in 0.12.1 to 0.11.x series for production installation.
Bug Release
- MIFOSX-311 - Zero % loan products or loan applications are not allowed due to validation checks
Focus on stabalising API and functionality around centers, groups and clients. Contains breaking changes in this API from the 0.11.x releases.
Note: known issue with existing set of reports provided out of box. Due to changes in client database columns for is_deleted (removed), joining_date (changed to activation_date) some of the reports do not work correctly at present. We will provide patches to update these.
Bugs
- [MIFOSX-262] - You can add a client to an office prior to the opening date of the office
Improvements/Features
- [MIFOSX-213] - Support client and group 'statuses' to enable approval workflows
- [MIFOSX-282] - Add min max constraints to loan product and enforce for loan application creation, disbursal
- [MIFOSX-247] - Savings account deposits
- [MIFOSX-248] - Savings account withdrawals
- [MIFOSX-290] - Groups api for centers/groups/communal banks
- [MIFOSX-277] - Add API Documentation for Loan Charges
- [MIFOSX-285] - Fix Api docs css
- [MIFOSX-288] - Improve documentation for charges
Bug Release.
- [MIFOSX-299] - Only super users are able to update client and loan documents
Bug Release.
- https://mifosforge.jira.com/browse/MIFOSX-292 - Retrieving an existing loan product does not return the correct value for decimalPlaces
- https://mifosforge.jira.com/browse/MIFOSX-293 - Calculating the Loan Schedule does not use the correct value for decimalPlaces
- https://mifosforge.jira.com/browse/MIFOSX-294 - Updating loan products min/max principal details incorrectly results in error message relating to interestRatePerPeriod
Bug Release.
- Revert back to hibernate 4.1.9.Final to allow datatables to be persisted
- MIFOSX-291 - unable to create office
Focus on Individual Lending with Cash Accounting, in development features such as centers, groups, savings accounts and accrual accounting in progress.
Known issues
- Due to https://jira.springsource.org/browse/SPR-10395 datatables not persisting correct
- Due to upgrade to hibernate 4.2, JPA specs more strict causing some entities to not persist correctly (https://mifosforge.jira.com/browse/MIFOSX-291)