... no problem... thanks a ton for detecting the issue and sorry again for the inconvenience. Not sure if I mentioned it: I'm currently developing a Gradle release plugin for Fineract that takes care of most of these steps we need to do for a release (ca. 15). As these releases don't happen (yet) that often it's easy to forget a step (or drop a parameter like I did when creating the tag). When we have that plugin in place it should be a lot less likely to drop the ball and it should be easier for others to jump in as a release manager (like Petri last year when I was not available to do it).
Just to say... this should get a lot better. Cheers, Aleks On Tue, Apr 26, 2022 at 7:35 PM Manoj VM <[email protected]> wrote: > Thank you very much for fixing this > Thanks and Regards, > Manoj > fynarfin.io > > > On Mon, Apr 25, 2022 at 12:33 PM Arnold Galovics <[email protected]> > wrote: > >> Thanks Aleks for the investigation and taking care of it. Appreciated. >> >> Best, >> Arnold >> >> On Sun, Apr 24, 2022 at 3:36 AM Aleksandar Vidakovic < >> [email protected]> wrote: >> >>> Hi everyone, >>> >>> ... just continuing in a fresh thread, because the topic "Fineract 1.5.0 >>> to 1.6.0" got too big for the list mailer daemon. >>> >>> Just wanted to repeat that the Git tag is corrected and shows the >>> correct history now (i. e. does not include the Liquibase commit). >>> >>> FYI >>> >>> Aleks >>> >> > 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. >
