Hi Frank, Yes, I'm seeing the same thing, and I hope someone on the mifos dev list can help clarify. @Shruti_Rajaram, @Santosh_Math, @Edward Cable <[email protected]> could weigh in. There may have been announcements on mifos-developer listserv that I missed!
To be clear, the two projects have a close relationship but are not the same. Fineract1.x is the backend solution with the community-app and other front ends (aka Channel solutions) provided by Mifos.org. I am cross-list posting this response. I believe that it is also true that these projects should be able to evolve somewhat separately, and that NOT every release in Fineract1.x has an equivalent release in Mifos community-app. As long as the APIs in new releases of finerct1.x remain backwards compatible (supports api version of earlier) of the community-app, then they can be developed out of phase if you will. That would be the ideal thing for incremental point and patch releases. >From the beginning of mifosX, the community-app only ever expressed a subset of the available functionality. That is, the APIs were more expressive than that used by the demo app. So, as to the Community-app status. On demo, it appears that the release = https://github.com/openMF/community-app/tree/MIFOSX-18.03.01.RELEASE-Patch. I see that: "17.07.01 Release" branch is 334 commits behind "develop"; "18.03.01.RELEASE-Patch" is one commit ahead and 100 behind "develop". "master" is 100 behind "develop". Since fineract is now officially at 1.2, mifos could create a "2019.02.xx RELEASE" that is aimed at supporting the features that are newly available in the latest fineract. Thanks, @jdailey67 On Thu, May 10, 2018 at 8:06 AM Frank Nkuyahaga <[email protected]> wrote: > Hi there, > > Could someone be so kind to point me to the GitHub repo for Community App > v18.x. I tried this but I’m getting v17.x —> > https://github.com/openMF/community-app < > https://github.com/openMF/community-app> > > Thanks in advance > > Frank
