Re: Let's prepare for 1.5.0...

2020-09-30 Thread Michael Vorburger
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, >

Re: Let's prepare for 1.5.0...

2020-09-30 Thread Aleksandar Vidakovic
+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...

2020-09-30 Thread Bharath Gowda
+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...

2020-09-30 Thread Ed Cable
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...

2020-09-30 Thread Awasum Yannick
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...

2020-09-30 Thread Michael Vorburger
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: Let's prepare for 1.5.0...

2020-09-30 Thread Aleksandar Vidakovic
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: Let's prepare for 1.5.0...

2020-09-30 Thread sifiso
+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 m

Re: Let's prepare for 1.5.0...

2020-10-01 Thread Airsay Longcon
ksandar 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 beginning > of January or end of December? Because then we could have "

Re: Let's prepare for 1.5.0...

2020-10-01 Thread Aleksandar Vidakovic
> > If there's any confusion I can clarify > > On 30 Sep 2020, at 17:25, sif...@skyburgsystems.org wrote: > >  > > +1 for a 3 month cycle. A lot more realistic considering the time it took > to release 1.4.0 > > > > > > *From:* Aleksandar Vidakovic

Re: Let's prepare for 1.5.0...

2020-10-02 Thread Airsay Longcon
As a follow up to this, I just found a way to "end" or "archive" savings products using the Entity to entity mapping. I don't know if this works for fixed deposit or Recurring Deposit products. I will investigate this and revert > On 1 Oct 2020, at 11:45, Aleksandar Vidakovic > wrote: >

Re: Let's prepare for 1.5.0...

2020-10-07 Thread Ed Cable
Airsay, Echoing what Aleks said, can you please add these to JIRA as feature requests and apply the fix version 1.5.0. https://issues.apache.org/jira/projects/FINERACT/summary Thanks, Ed On Fri, Oct 2, 2020 at 9:03 AM Airsay Longcon wrote: > As a follow up to this, I just found a way to "end

Re: Let's prepare for 1.5.0...

2020-10-08 Thread airsay longcon
Done On Wed, 7 Oct 2020 at 14:31, Ed Cable wrote: > Airsay, > > Echoing what Aleks said, can you please add these to JIRA as feature > requests and apply the fix version 1.5.0. > > https://issues.apache.org/jira/projects/FINERACT/summary > > Thanks, > > Ed > > On Fri, Oct 2, 2020 at 9:03 AM Airs