Hello everyone, We currently have 111 open issues with Fix Version 1.5.0, see https://issues.apache.org/jira/issues/?jql=project%20%3D%20%22Apache%20Fineract%22%20AND%20resolution%20is%20EMPTY%20and%20fixVersion%20%3D%201.5.0%20%20ORDER%20by%20status%20DESC%2C%20priority%20DESC%2C%20updated%20DESC
Could we invite any active contributors who have open issues with Fix Version 1.5.0 assigned to yourself EITHER link them to https://issues.apache.org/jira/browse/FINERACT-1305 if you are actively working on them and about to raise a PR, OR remove the 1.5.0 fix version if it's not going to make it for this next release? (I've just done this for all issues that were assigned to me.) Note that the way that this process (has to) work is that only active contributors set Fix Versions; so this is about "I can commit to fixing XYZ" and NOT about "I would like XYZ to be fixed for XYZ - but cannot fix it myself (or pay someone to fix it for me)"... otherwise we would probably never ship. The Release Manager (RM, Aleks) will just remove the Fix Version 1.4.0 for anything that doesn't make it, as per https://cwiki.apache.org/confluence/display/FINERACT/How+to+Release+Apache+Fineract . Best, M. _______________________ Michael Vorburger http://www.vorburger.ch On Tue, Jan 26, 2021 at 2:09 PM Aleksandar Vidakovic < chee...@monkeysintown.com> wrote: > Hi everyone, > > Based on our "How to Release Apache Fineract" process documented at > https://cwiki.apache.org/confluence/x/DRwIB : > > I will create a 1.5.0 branch off develop in our git repository at > https://github.com/apache/fineract on Wednesday, February 10, 2020. > > The release tracking umbrella issue for tracking all activity in JIRA is > https://issues.apache.org/jira/browse/FINERACT-1305 for this Fineract > 1.5.0. > > If you have any work in progress that you like to see included in this > release, please add "blocking" links to the release JIRA issue. > > I am the release manager for this release. > > Cheers, > > Aleks >
