Devs - THIS IS NOT a VOTE Resurfacing this release thread. Once we have completed this Release 1.10 .1 we will move to release 1.11 immediately, to catch up. Heads up coming soon.
Release 1.10 will be - backdated - to the release tag of April 26th. It will also technically be called release 1.10.1 as it includes a small change that came after my tag on git. Before I call for a vote on the release, I would ask that anyone who worked on the tickets between Jan and April 2024 please take a look at this summary and suggest points to make about the release. https://cwiki.apache.org/confluence/display/FINERACT/1.10.0+-+Apache+Fineract Summary of changes: (Please update the Jira if you had a ticket fully closed by April 30, 2024 . Please mark the resolved as tag 1.10.0). - General bug fixes between January 2024 and April 2024. - A number of improvements in the Progressive Loan module including Installment level delinquency, chargeback logic, and advanced allocation strategies. - Fixes to a number of things that were part of the 1.9 release, like overpayment calculation, and credit allocation, making this a likely stable release point. - New inline COB transaction handling. - Start of the modularization effort, but no major shifts. - All told there were about 120 commits during this period. https://cwiki.apache.org/confluence/display/FINERACT/1.10.0+-+Apache+Fineract As a heads up I am considering calling for a vote this weekend, with a requirement that a few PMC members are able to do that particular build and verify it. While this will be good to get out, there’s a lot more in release 1.11. Thanks, James On Thu, Aug 22, 2024 at 1:44 PM James Dailey <jdai...@apache.org> wrote: > Hi All - > > With Aleks' assistance, we (Aleks and I) are picking this up again. > > So, heads up again that we are going to use the tag dated 26-April-2024, > which I originally gave a heads up on as our point in time for this > release. > It fixed certain things and, importantly, is before a new dev effort > started. > > We will soon receive an email from Aleks calling for a VOTE on the release > 1.10.1. > When you vote, please indicate what steps you took to verify that the > release is acceptable. > > We also note that the process we use to do a release needs improvement - > it has required ceremony and some legacy things that make it hard to > follow. > Some of this is because ASF (apache software foundation) has some > requirements, but also because perhaps we have taken some things as > requirements that are not that. > I will have more to say on that after this release. > > If this release is accepted, and goes forward, we will also begin (soon) a > discussion about the next release. > Philosophically, I believe that a release should be possible at any point > in time, as the build should be stable at all times. > In those rare times that the build is failing, we don't do a release, > obviously. > > Thank you > - James > >
