[
https://issues.apache.org/jira/browse/FINERACT-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17077286#comment-17077286
]
Vishwas Babu A J commented on FINERACT-877:
-------------------------------------------
[~vorburger] : Release 1.3.0 was broken. Any app (Mobile or web) could not
connect to this release due to a CORS issue. The issue was caused by
[https://github.com/apache/fineract/commit/eb5ad448fa6cb365dad7e2691f4c6f7e9bb1c196]
. The 1.3.1 branch was setup for making a hot fix release with only one
change, i.e reverting the commit causing the CORS issue. This patch release has
not been shipped. I am assuming nobody is using the 1.3.0 release (given that
any app cannot connect to it)
> Clarify Fineract Version 1.3.1
> ------------------------------
>
> Key: FINERACT-877
> URL: https://issues.apache.org/jira/browse/FINERACT-877
> Project: Apache Fineract
> Issue Type: Bug
> Reporter: Michael Vorburger
> Priority: Major
>
> In JIRA, there is a 1.3.1 version, but it was never released.
> I doubt a 1.3.1 will be released (anyone?) - if anything, a 1.4.0, see
> FINERACT-873.
> There were 3 issues marked Fixed Version 1.3.1 today: FINERACT-755, and
> FINERACT-848 & FINERACT-832. The latter two have no PRs and so certainly
> never were for 1.3.1, the Report must have just not known which Fix Version
> to set; so I've just removed 1.3.1 from those two.
> The FINERACT-755 is more interesting - I don't fully understand yet is that
> is also in develop, or not.
> Shall we delete the 1.3.1 version in JIRA? And in git, after clarifying
> FINERACT-755 ?
> [~vishwasbabu] [~angelboxes]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
