Perfect, thanks a ton. On Fri, Aug 7, 2020 at 3:01 PM Percy Enoabane <[email protected]> wrote:
> Will create the Jira issues and link them to FINERACT-826. > > On Fri, Aug 7, 2020 at 10:29 AM Aleksandar Vidakovic < > [email protected]> wrote: > >> Hi Percy, >> >> ... yes, everything that is related to FINERACT-826 should then be moved >> to v1.5.0. I've updated your Jira task to reflect the correct version >> number (moved from v1.4.0 to v1.5.0). >> >> Could you let me know which Jira issues/PRs are related to FINERACT-826? >> Then we can mark and organize them accordingly (to save some time for the >> next release cycle). >> >> Thanks again for the heads-up and your help. >> >> Cheers, >> >> Aleks >> >> On Fri, Aug 7, 2020 at 10:23 AM Percy Enoabane <[email protected]> >> wrote: >> >>> Hi Aleks, >>> >>> There is some work <https://github.com/apache/fineract/pull/1179> in >>> progress targeted for v1.5.0(to avoid any "risk" upcoming 1.4.0). >>> Subsequent work on PRs that depend on this to be merged in the develop >>> branch should only come after the v1.4.0 branch is created? >>> >>> Percy >>> >>> On Wed, Aug 5, 2020 at 2:19 PM Aleksandar Vidakovic < >>> [email protected]> 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 v1.4.0 branch off develop in our git repository at >>>> https://github.com/apache/fineract on Thursday, August 20, 2020. >>>> >>>> The release tracking umbrella issue for tracking all activity in JIRA >>>> is https://issues.apache.org/jira/browse/FINERACT-873 for this >>>> Fineract v1.4.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 >>>> >>>
