+0 neutral I would like us to take this a bit slower.
Some companies (Users) running Fineract in production may need several weeks to months to implement such a change on their infrastructure. It potentially has implications regarding testing, security, and compliance. If we are serious about meeting the needs in the financial sector such considerations are normal and expected. So, while I 100% support the change, I think we need to give Users at least a three-month heads-up before significant changes of this nature. I would like to propose that for some period of time (30 days?), the upgraded java version is held in a separate branch from the main dev and that issues are identified and resolved there, subsequently a merge occurs, then it goes into the Main branch. I realize that may sound like overkill, but I believe that it helps maintain good communication. i.e. "This is coming, it is actually here... counting down the days..." type of thing. Is this a FSIP? - Fineract Significant Improvement Proposal. When implementing something that could significantly impact users, we should use that process and effectively give notice. On Thu, Aug 6, 2026 at 1:16 PM Adam Monsen <[email protected]> wrote: > +1 >
