Devs - I started the release process but became aware of a blocker to that - so we are delayed. *Please help to stabilize the code base by Friday, Feb 21st.*
AND, looking at the commit log and the Jira tickets, what am I to make of only 35 tickets in Jira (fixVersion = 1.11.0) and roughly 350 commits and PRs in the GitHub log? See https://cwiki.apache.org/confluence/display/FINERACT/1.11.0+%28Pre-+Release+work%29+-+Apache+Fineract . It cannot be the job of the Release Manager to make sure that the processes are being followed. The project needs everyone to follow good project hygiene so that it can be maintained and understood. Can we please discuss how to improve that? My starting point was "Please make sure your tickets that were closed between May 1st, 2024 and February 5th, 2025 (NOW) are tagged with FixVersion=1.11.0." But, I think the problem is probably deeper than that. Comment. James On Sun, Jan 26, 2025 at 6:44 PM James Dailey <jdai...@apache.org> wrote: > Hello everyone, > > I am the Release Manager for this next release. > > Based on our "How to Release Apache Fineract" process documented at > https://cwiki.apache.org/confluence/x/DRwIB, I will create a Release 1.11 > branch off develop in our git repository at > https://github.com/apache/fineract on > > ==> FEBRUARY 5th, 2025 > > The release tracking umbrella issue for tracking all activity in JIRA is > https://issues.apache.org/jira/browse/FINERACT-2172 > <https://issues.apache.org/jira/browse/FINERACT-2172> > > If you have any work in progress that you would like to see included in > this release, please add "blocking" links to the release JIRA issue. > > I'll add that as far as I know, this is a good moment with key features > reaching some maturity and a lot of development happening since the release > 1.10.1 (which was a branch freeze around May 1, 2024). This is not a > request to stop development, but please be aware of the branch being > created on February 5th, 2025 at 1700 GMT. > > Cheers, > James > >
