...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. >>> >>
