Re: Finereract Customization

+1 on Petri's suggestion Swagger should show "1.4.0" And thanks for the PR On Wed, Sep 30, 2020 at 9:12 AM Petri Tuomola wrote: > OK - I’ve submitted PR https://github.com/apache/fineract/pull/1359 to > fix this. > > Btw just looking at the tag done for release 1.4.0 - could we make the > rel

RE: Let's prepare for 1.5.0...

+1 for a 3 month cycle. A lot more realistic considering the time it took to release 1.4.0 From: Aleksandar Vidakovic Sent: Wednesday, 30 September 2020 5:25 PM To: Dev Subject: Re: Let's prepare for 1.5.0... I like the 3 month cycle... for this "first" cycle maybe we can aim beginn

Re: Finereract Customization

OK - I’ve submitted PR https://github.com/apache/fineract/pull/1359 to fix this. Btw just looking at the tag done for release 1.4.0 - could we make the release tag to be “1.4.0” (i.e. not “release-1.4.0”) so that it would be consistent with the pre

Re: Finereract Customization

Hi I’ve just reproduced this: looks like the build fails if you are not building from within a git repository, as it can’t find the git properties for population into Swagger version number. Shouldn’t be difficult to fix though - I’ll have a look and send a PR asap. Regards Petri > On 30 Sep

Re: Let's prepare for 1.5.0...

I like the 3 month cycle... for this "first" cycle maybe we can aim beginning of January or end of December? Because then we could have "nice" predictable release dates in January, March, June, September... Also agree with Michael's no code freezes... backporting worked nicely in 1.4.0 On Wed, Se

Re: Finereract Customization

Tube (?), This is an interesting new problem that we are not yet aware of; thank you for sharing it with us on the list (that's one good way of contributing and helping the project). Are you seeing this problem after a "git clone", or with sources that you downloaded as a ZIP file? From where, ho

Re: Let's prepare for 1.5.0...

Targeting a 3 months cycle sounds good to me, and longer term perhaps more realistic than 2 months? So I would suggest 3, for now; possible reduction to a 2 months window later, if our contributions suddenly explode... ;-) More specifically, when exactly do you want to start counting? The date of

RE: Finereract Customization

Mhretaab, Your concern to externalise the password for mysql is based on a security issue? Up to now we’ve never had issues with the password because deployments are always locally hosted then broadcasted for remote access on a private connection. So its never really exposed and works quit

RE: Digital Banking UI available at enlistabank

Hi Ed, I’d like to get involved in contributing towards this. Is it going to revolve around deposit products or grow out into a fully-fledged Mifos web-app? Pls note: The login details were working just two days ago but they don’t seem to be working now. Kind regards, Sifiso Fr

Re: Let's prepare for 1.5.0...

Michael, that is a good idea. Ed maybe we could do a release once every 2 or 3 months. A monthly release wont have alot of features based on the contribution rate. But doing it once every 2 or 3 months will have a sizeable list of bug fixes. What do you all think? On Wed, Sep 30, 2020, 14:06 Ed

Re: Let's prepare for 1.5.0...

Hi Michael, I think it would be good to aim for a time-boxed release cadence. That is what we were aiming for before but I think given we had no release manager and no steady review of PRs, the aim of bi-monthly releases was too ambitious. What would you propose as a frequency of release cycle? -

Re: Let's prepare for 1.5.0...

+1 It's a great thought, codebase would become more stable with timely fixes and release. also, organizations can plan their work according to the release date. Regards, Bharath Lead Implementation Analyst | Mifos Initiative Skype: live:cbharath4| Mobile: +91.7019636073 http://mifos.org

Re: Let's prepare for 1.5.0...

+1 ... like it. On Wed, Sep 30, 2020 at 1:09 PM Michael Vorburger wrote: > Hello, > > I have an idea/proposal, for discussion/input: > > How crazy would it be to suggest a strictly time boxed release cadence for > Fineract? > > So we would discuss and agree upon a DATE instead of SCOPE for 1.5.0

Re: Let's prepare for 1.5.0...

Hello, I have an idea/proposal, for discussion/input: How crazy would it be to suggest a strictly time boxed release cadence for Fineract? So we would discuss and agree upon a DATE instead of SCOPE for 1.5.0. Best, M. On Wed, 30 Sep 2020, 08:54 Aleksandar Vidakovic, wrote: > Hi everyone, >