Adam - Do we have a commit in hand?
James On Fri, Oct 3, 2025 at 8:18 AM Kapil Panchal < [email protected]> wrote: > I think what is the need of the hour is to have a *Release Alignment > Strategy*. Do we have a release plan that coincides with the release of > all major dependency releases? e.g. Java releases its LTS every 3 years > around September? SpringBoot follows a rough release cycle of 6 month with > releases every May and November? A nice to have would be a plan that > follows these major releases. It also makes it more credible, dependable > and gives confidence of a matured and stable product? > > On Fri, Oct 3, 2025 at 12:49 PM Ádám Sághy <[email protected]> wrote: > >> Hi James, >> >> I dont disagree, but we have a couple way too early work. >> >> Let me give a try to find a commit which is the most “reliable”, maybe >> cherry pick a little. >> >> Regards, >> Adam >> >> On 2025. Oct 2., at 18:37, James Dailey <[email protected]> wrote: >> >> Hi Adam - Thanks. >> >> Today might be a good day to grab a commit point for the release. AFAIK, >> the devs have finished some features as of yesterday and pushed some >> additional clean up commits. There is always dev going on, so the task is >> not to find the "perfect" point but one where the features are working well >> enough for 90% of the users. I think that point is today. >> >> Does anyone disagree? >> >> >> On Mon, Sep 29, 2025 at 2:44 PM Adam Monsen <[email protected]> wrote: >> >>> Thanks James. I'm happy to do this and I'm ready to start whenever. >>> >>> https://fineract.apache.org/docs/current/#_releases outlines a roughly >>> 17-day process, so I'd expect the same for this release. >>> >>> *I need advice on when's a good time to start the process, and which >>> commit to start from for the release branch*. @Ádám Sághy >>> <[email protected]>, would you please advise? >>> >>> Release process streamline idea: We can branch for the release from any >>> point we choose, so if we happen to have a known good commit (has all the >>> right/complete features, none we don't want, and all tests passed) already, >>> maybe we could use it as-is and shorten the release branch stabilization >>> time. I'd guess the chance of this is small. >>> >>> re: automating the release process: Yep. This needs more/dedicated >>> ideas/research/testing. >>> >>> On Fri, Sep 19, 2025 at 3:32 PM James Dailey <[email protected]> >>> wrote: >>> >>>> I’ve asked Adam Monsen to again be the release manager - we have some >>>> issues to get into an official release. Can we get this out by Oct 7th? >>>> >>>> We are seeking to make the release process more streamlined and >>>> automated as well. >>>> >>>> As part of this we will likely roll release 1.12.x to end of life. >>>> Some important improvements like oauth changes cannot be backported. >>>> >>>> >>>> >>>> >>
