... to avoid confusion I'll rename the existing branches already now... it's just easier later on.
This means: - current 1.7.1 (git hash 8ef6bc0fd15561c1392b0be881f1e3e51c4b1809) becomes 1.7.2 - current 1.8.1 (git hash f3ba438bd7bf60f5a55ab549379d1abe3039a431) becomes 1.8.2 On Tue, Nov 22, 2022 at 2:33 AM Aleksandar Vidakovic < [email protected]> wrote: > Hi all, > > ... we have to postpone Manoj's changes for a moment (sorry @Manoj VM > <[email protected]> ) to get another important improvement out before. We > will leave Manoj's improvements (and associated branches 1.8.1 and 1.7.1) > as is for now to minimize extra work and will take care of a proper release > shortly after this one is out. > > I will create branches 1.8.1.0 and 1.7.1.0 (just for giving them a > different name) for the upcoming release and will send out announcements > shortly. > > Cheers, > > Aleks > > On Tue, Nov 15, 2022 at 7:30 AM Manoj VM <[email protected]> wrote: > >> ...The release branches 1.7.1 and 1.8.1 are active and these branches >> will be used to release 1.7.1 and 1.8.1 as mentioned in the other >> communication. ( >> https://lists.apache.org/thread/kq9sxl53bgo21ppghxf1xjmjoz0rwf0b >> <https://lists.apache.org/thread/kq9sxl53bgo21ppghxf1xjmjoz0rwf0b>) >> >> Thanks and Regards, >> Manoj >> fynarfin.io >> >> >> On Tue, Nov 15, 2022 at 11:57 AM Manoj VM <[email protected]> wrote: >> >>> ...We have to remove the tag 1.7.1 ( manually released) that is >>> currently available in Fineract(GitHub) and re-release it. >>> >>> Thanks and Regards, >>> Manoj >>> fynarfin.io >>> >>> >>> On Mon, Nov 14, 2022 at 11:52 PM James Dailey <[email protected]> >>> wrote: >>> >>>> For the avoidance of confusion, this release process was further >>>> discussed on this thread ==>. >>>> https://lists.apache.org/thread/kq9sxl53bgo21ppghxf1xjmjoz0rwf0b >>>> <https://lists.apache.org/thread/kq9sxl53bgo21ppghxf1xjmjoz0rwf0b> >>>> >>>> 1.7.1 was not released >>>> >>>> Thank you Manoj for taking this on. >>>> >>>> >>>> >>>> On Mon, Nov 7, 2022 at 6:47 PM Manoj VM <[email protected]> wrote: >>>> >>>>> >>>>> Hello everyone, >>>>> >>>>> ... based on our "How to Release Apache Fineract" process documented >>>>> at https://cwiki.apache.org/confluence/x/DRwIB: >>>>> >>>>> I have created a 1.7.1 branch off 1.7.0 release in our git repository >>>>> at https://github.com/apache/fineract on Tuesday, November 8, 2022. >>>>> >>>>> The release tracking umbrella issue for tracking all activity in JIRA >>>>> is FINERACT-1799 (https://issues.apache.org/jira/browse/FINERACT-1799) >>>>> for this Fineract 1.7.1. >>>>> >>>>> 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 am the release manager for this release. >>>>> >>>>> Cheers, >>>>> >>>>> Manoj Mohanan >>>>> >>>>> >>>>> >>>>> 🎉 Powered by Fineract Release Plugin 🎊 >>>>> >>>>> >>>>> Disclaimer: >>>>> >>>>> Privileged & confidential information is contained in this message >>>>> (including all attachments). If you are not an intended recipient of this >>>>> message, please destroy this message immediately and kindly notify >>>>> the sender by reply e-mail. Any unauthorised use or dissemination of >>>>> this message in any manner whatsoever, in whole or in part, is strictly >>>>> prohibited. This e-mail, including all attachments hereto, (i) is for >>>>> discussion purposes only and shall not be deemed or construed to be a >>>>> professional opinion unless expressly stated otherwise, and (ii) is not >>>>> intended, written or sent to be used, and cannot and shall not be used, >>>>> for >>>>> any unlawful purpose. This communication, including any attachments, may >>>>> not be free of viruses, interceptions or interference, and may not be >>>>> compatible with your systems. You should carry out your own virus checks >>>>> before opening any attachment to this e-mail. The sender of this e-mail >>>>> and >>>>> *Fynarfin Tech Private Limited* shall not be liable for any damage >>>>> that you may sustain as a result of viruses, incompleteness of this >>>>> message, a delay in receipt of this message or computer problems >>>>> experienced. >>>>> >>>>
