Reviving this thread. Sounds good James, thank you, I didn't know that. Yes, I am willing to be release manager for v1.12.0. Let me know what the ceremony is for becoming the release manager, if any.
I created an umbrella ticket for the release: https://issues.apache.org/jira/browse/FINERACT-1811 v1.11.0 was released on March 9th <https://lists.apache.org/thread/jn00ybtg148rqxno9sr1qdg0cqxktoht>. Per our goal of quarterly releases, we should aim to have v1.12.0 released by June. Agreed? Assuming June 1 release date, let's start talking about what date we'd want to target for creating the release candidate and allowing time for the rest of the release process to be able to hit that date. I'm also assuming we're just doing another "pick a good point in time"-style release of a commit on the develop branch (one passing all tests, etc). On Fri, Apr 4, 2025 at 1:57 PM James Dailey <jamespdai...@gmail.com> wrote: > Technically you do not have to be a Committer to be a Release Manager > (although it is much easier with the rights). > > On Fri, Apr 4, 2025 at 1:54 PM Adam Monsen <amon...@mifos.org> wrote: > >> James wrote: >> >>> Adam - do you wish to propose yourself as the Release Manager? >> >> >> Sure! Assuming Ed supports this. >> >> I'm happy to work with you or another committer as I have with 1.10.1 and >> 1.11.0, or become a committer and do more/all of the release work. I'll >> need help with some bits and bobs e.g. "clean up JIRA", but it seems doable. >> >> We should improve the release process itself along with actually shipping >> periodic releases. >> >
