Re: [FINERACT] [PROPOSAL]  New release 1.7.0

[Aleksandar Vidakovic]

Hi everyone,

... we just merged the build fix into the develop branch. Please rebase
your open PRs (or forks) and pull in the fixes.

Note: there's a small rearrangement concerning the dependency (version)
management... you'll find the definitions now in
[FINERACT]/buildSrc/src/main/groovy/org.apache.fineract.dependencies.gradle;
the reason for that is that the dependency management is now shared with
the new Fineract Gradle plugin (used to assist with releases and publishing
of documentation).

FYI

Cheers,

Aleks

On Thu, May 5, 2022 at 11:33 PM Aleksandar Vidakovic 
wrote:

> Hi everyone,
>
> ... it took a moment to get this right, but I think we have a solution for
> the recent build issues. It took a bit longer, because I decided to finally
> get rid of all Gradle console warnings concerning optimization issues
> (usually that means that the Gradle cache for certain tasks/modules was
> deactivated to ensure correct results). We have none of these anymore...
> and my subjective tests show major improvements (no unnecessary builds of
> modules that have no changes etc.). There is one exception: the extraction
> of the Swagger/OpenApi manifest is always quite busy... the corresponding
> Gradle plugin is probably just not implemented with cache support; was
> already like that before. I'll see later if I can improve that one even
> more.
>
> So... I'm just waiting now for a second pair of eyes to confirm these
> observations... and then we can start the release process for real. BTW: I
> think Arnold has his fix for the Mysql syntax issues also lined up,
> probably just blocked by my pull request here.
>
> If you want to have a look for yourself:
> https://github.com/apache/fineract/pull/2313
>
> Tomorrow morning (GMT+2) we should be back to normal (actually in a little
> bit better shape due to better build cache support). Any feedback is as
> usual welcome.
>
> Cheers,
>
> Aleks
>
> On Thu, May 5, 2022 at 10:37 AM hitesh prajapati <
> hitesh.kams.prajap...@gmail.com> wrote:
>
>> Hi Aleks,
>>
>> This makes sense and thanks for your effort for this.
>>
>>
>>
>> On Thu, 5 May 2022, 13:11 Arnold Galovics,  wrote:
>>
>>> Hi Hitesh,
>>>
>>> Thanks for the diligence, we appreciate it.
>>> I'm already working on a solution that's more widespread to the problem
>>> and will avoid future issues like this because there are a couple other
>>> places too where I see the same issue.
>>>
>>> Best,
>>> Arnold
>>>
>>> On Thu, May 5, 2022 at 9:05 AM hitesh prajapati <
>>> hitesh.kams.prajap...@gmail.com> wrote:
>>>
 Hi Aleks, Arnold,

 I can raise the PR for the issue which I fixed
 for ReportWritePlatformServiceImpl as described in my previous email if
 that helps.

 Thanks,
 Hitesh

 On Thu, May 5, 2022 at 12:17 PM hitesh prajapati <
 hitesh.kams.prajap...@gmail.com> wrote:

> Hi Aleks, Arnold,
>
> I did encounter similar issue where the below INSERT SQL  failed for
> the below call because grouping is a keyword in MySQL 8.
> So I changed this particular call from repository to jdbc template.
>
> permissionRepository.save(permission) call from public interface 
> PermissionRepository
> extends JpaRepository
>
> INSERT INTO m_permission (action_name, can_maker_checker, code, 
> entity_name, grouping)
> VALUES ('READ', 0, 'READ_Mifos Balance and Transactions Report', 'Mifos 
> Balance and Transactions Report',
> 'report')
>
>
>
> On Thu, May 5, 2022 at 4:43 AM Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> Hi everyone,
>>
>> ... just wanted to inform everyone about the upcoming release. We'll
>> probably need another day or so until I'll open the release branch. We 
>> had
>> some reports of SQL syntax errors on certain MySQL instances (Arnold is
>> working on that) and at the moment there's a sneaky build issue in the
>> develop branch that I'm trying to fix.
>>
>> If we solve these issues in the predicted time frame then we are
>> still on target with the May 10 release date (more or less).
>>
>> Just FYI.
>>
>> Cheers,
>>
>> Aleks
>>
>> On Wed, Apr 27, 2022 at 4:31 PM Aleksandar Vidakovic <
>> chee...@monkeysintown.com> wrote:
>>
>>> Hi everyone,
>>>
>>> ... friendly reminder that we have an upcoming release. I am going
>>> to open a release branch probably tomorrow. Until then please cleanup 
>>> your
>>> tickets for this release. I will start triaging the tickets today and
>>> tomorrow and move everything that's not finished to the next release.
>>>
>>> Please reach out to me if you have any questions or concerns.
>>>
>>> FYI
>>>
>>> Cheers,
>>>
>>> Aleks
>>>
>>> On Thu, Apr 21, 2022 at 12:22 AM Aleksandar Vidakovic <
>>> chee...@monkeysintown.com> wrote:
>>>
 ... great... the current list of tickets is 

Re: [FINERACT] [PROPOSAL]  New release 1.7.0

[Aleksandar Vidakovic]

Hi everyone,

... it took a moment to get this right, but I think we have a solution for
the recent build issues. It took a bit longer, because I decided to finally
get rid of all Gradle console warnings concerning optimization issues
(usually that means that the Gradle cache for certain tasks/modules was
deactivated to ensure correct results). We have none of these anymore...
and my subjective tests show major improvements (no unnecessary builds of
modules that have no changes etc.). There is one exception: the extraction
of the Swagger/OpenApi manifest is always quite busy... the corresponding
Gradle plugin is probably just not implemented with cache support; was
already like that before. I'll see later if I can improve that one even
more.

So... I'm just waiting now for a second pair of eyes to confirm these
observations... and then we can start the release process for real. BTW: I
think Arnold has his fix for the Mysql syntax issues also lined up,
probably just blocked by my pull request here.

If you want to have a look for yourself:
https://github.com/apache/fineract/pull/2313

Tomorrow morning (GMT+2) we should be back to normal (actually in a little
bit better shape due to better build cache support). Any feedback is as
usual welcome.

Cheers,

Aleks

On Thu, May 5, 2022 at 10:37 AM hitesh prajapati <
hitesh.kams.prajap...@gmail.com> wrote:

> Hi Aleks,
>
> This makes sense and thanks for your effort for this.
>
>
>
> On Thu, 5 May 2022, 13:11 Arnold Galovics,  wrote:
>
>> Hi Hitesh,
>>
>> Thanks for the diligence, we appreciate it.
>> I'm already working on a solution that's more widespread to the problem
>> and will avoid future issues like this because there are a couple other
>> places too where I see the same issue.
>>
>> Best,
>> Arnold
>>
>> On Thu, May 5, 2022 at 9:05 AM hitesh prajapati <
>> hitesh.kams.prajap...@gmail.com> wrote:
>>
>>> Hi Aleks, Arnold,
>>>
>>> I can raise the PR for the issue which I fixed
>>> for ReportWritePlatformServiceImpl as described in my previous email if
>>> that helps.
>>>
>>> Thanks,
>>> Hitesh
>>>
>>> On Thu, May 5, 2022 at 12:17 PM hitesh prajapati <
>>> hitesh.kams.prajap...@gmail.com> wrote:
>>>
 Hi Aleks, Arnold,

 I did encounter similar issue where the below INSERT SQL  failed for
 the below call because grouping is a keyword in MySQL 8.
 So I changed this particular call from repository to jdbc template.

 permissionRepository.save(permission) call from public interface 
 PermissionRepository
 extends JpaRepository

 INSERT INTO m_permission (action_name, can_maker_checker, code, 
 entity_name, grouping)
 VALUES ('READ', 0, 'READ_Mifos Balance and Transactions Report', 'Mifos 
 Balance and Transactions Report',
 'report')



 On Thu, May 5, 2022 at 4:43 AM Aleksandar Vidakovic <
 chee...@monkeysintown.com> wrote:

> Hi everyone,
>
> ... just wanted to inform everyone about the upcoming release. We'll
> probably need another day or so until I'll open the release branch. We had
> some reports of SQL syntax errors on certain MySQL instances (Arnold is
> working on that) and at the moment there's a sneaky build issue in the
> develop branch that I'm trying to fix.
>
> If we solve these issues in the predicted time frame then we are still
> on target with the May 10 release date (more or less).
>
> Just FYI.
>
> Cheers,
>
> Aleks
>
> On Wed, Apr 27, 2022 at 4:31 PM Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> Hi everyone,
>>
>> ... friendly reminder that we have an upcoming release. I am going to
>> open a release branch probably tomorrow. Until then please cleanup your
>> tickets for this release. I will start triaging the tickets today and
>> tomorrow and move everything that's not finished to the next release.
>>
>> Please reach out to me if you have any questions or concerns.
>>
>> FYI
>>
>> Cheers,
>>
>> Aleks
>>
>> On Thu, Apr 21, 2022 at 12:22 AM Aleksandar Vidakovic <
>> chee...@monkeysintown.com> wrote:
>>
>>> ... great... the current list of tickets is not too long (not too
>>> short either)... 65... plenty of room to add... and some of the issues 
>>> that
>>> are currently included will move to the next release (mostly stale 
>>> stuff)
>>> very likely... so, no problem.
>>>
>>> On Thu, Apr 21, 2022 at 12:12 AM Ed Cable  wrote:
>>>
 Aleks,

 I will check with Manoj and Avik from Fynarfin to see if there are
 any changes that are being worked on that might be ready for inclusion 
 into
 1.7.

 Ed

 On Wed, Apr 20, 2022 at 2:34 PM Aleksandar Vidakovic <
 chee...@monkeysintown.com> wrote:

> @Victor Manuel Romero Rodriguez  your
> three tickets are 

Re: [FINERACT] [PROPOSAL]  New release 1.7.0

[hitesh prajapati]

Hi Aleks,

This makes sense and thanks for your effort for this.



On Thu, 5 May 2022, 13:11 Arnold Galovics,  wrote:

> Hi Hitesh,
>
> Thanks for the diligence, we appreciate it.
> I'm already working on a solution that's more widespread to the problem
> and will avoid future issues like this because there are a couple other
> places too where I see the same issue.
>
> Best,
> Arnold
>
> On Thu, May 5, 2022 at 9:05 AM hitesh prajapati <
> hitesh.kams.prajap...@gmail.com> wrote:
>
>> Hi Aleks, Arnold,
>>
>> I can raise the PR for the issue which I fixed
>> for ReportWritePlatformServiceImpl as described in my previous email if
>> that helps.
>>
>> Thanks,
>> Hitesh
>>
>> On Thu, May 5, 2022 at 12:17 PM hitesh prajapati <
>> hitesh.kams.prajap...@gmail.com> wrote:
>>
>>> Hi Aleks, Arnold,
>>>
>>> I did encounter similar issue where the below INSERT SQL  failed for the
>>> below call because grouping is a keyword in MySQL 8.
>>> So I changed this particular call from repository to jdbc template.
>>>
>>> permissionRepository.save(permission) call from public interface 
>>> PermissionRepository
>>> extends JpaRepository
>>>
>>> INSERT INTO m_permission (action_name, can_maker_checker, code, 
>>> entity_name, grouping)
>>> VALUES ('READ', 0, 'READ_Mifos Balance and Transactions Report', 'Mifos 
>>> Balance and Transactions Report',
>>> 'report')
>>>
>>>
>>>
>>> On Thu, May 5, 2022 at 4:43 AM Aleksandar Vidakovic <
>>> chee...@monkeysintown.com> wrote:
>>>
 Hi everyone,

 ... just wanted to inform everyone about the upcoming release. We'll
 probably need another day or so until I'll open the release branch. We had
 some reports of SQL syntax errors on certain MySQL instances (Arnold is
 working on that) and at the moment there's a sneaky build issue in the
 develop branch that I'm trying to fix.

 If we solve these issues in the predicted time frame then we are still
 on target with the May 10 release date (more or less).

 Just FYI.

 Cheers,

 Aleks

 On Wed, Apr 27, 2022 at 4:31 PM Aleksandar Vidakovic <
 chee...@monkeysintown.com> wrote:

> Hi everyone,
>
> ... friendly reminder that we have an upcoming release. I am going to
> open a release branch probably tomorrow. Until then please cleanup your
> tickets for this release. I will start triaging the tickets today and
> tomorrow and move everything that's not finished to the next release.
>
> Please reach out to me if you have any questions or concerns.
>
> FYI
>
> Cheers,
>
> Aleks
>
> On Thu, Apr 21, 2022 at 12:22 AM Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> ... great... the current list of tickets is not too long (not too
>> short either)... 65... plenty of room to add... and some of the issues 
>> that
>> are currently included will move to the next release (mostly stale stuff)
>> very likely... so, no problem.
>>
>> On Thu, Apr 21, 2022 at 12:12 AM Ed Cable  wrote:
>>
>>> Aleks,
>>>
>>> I will check with Manoj and Avik from Fynarfin to see if there are
>>> any changes that are being worked on that might be ready for inclusion 
>>> into
>>> 1.7.
>>>
>>> Ed
>>>
>>> On Wed, Apr 20, 2022 at 2:34 PM Aleksandar Vidakovic <
>>> chee...@monkeysintown.com> wrote:
>>>
 @Victor Manuel Romero Rodriguez  your
 three tickets are included... FYI

 On Wed, Apr 20, 2022 at 11:27 PM Aleksandar Vidakovic <
 chee...@monkeysintown.com> wrote:

> @Victor Manuel Romero Rodriguez  ...
> no problem, I'll add them right now
>
> On Wed, Apr 20, 2022 at 11:19 PM VICTOR MANUEL ROMERO RODRIGUEZ <
> victor.rom...@fintecheando.mx> wrote:
>
>> Hello Aleks,
>>
>> Is it possible to include these PRs?
>>
>> FINERACT-1577 TLS support in fully managed serverless
>> environments
>> FINERACT-1576 GCP Cloud SQL Support
>> FINERACT-1575 IPv6 workaround
>>
>> Regards
>>
>> El mié, 20 abr 2022 a las 16:17, Ed Cable ()
>> escribió:
>>
>>> Thank you Aleks and glad to see all of the automation that you
>>> have added to the release process.
>>>
>>> Ed
>>>
>>> On Wed, Apr 20, 2022, 14:11 Aleksandar Vidakovic <
>>> al...@apache.org> wrote:
>>>
 Hello everyone,

 Based on our "How to Release Apache Fineract" process
 documented at https://cwiki.apache.org/confluence/x/DRwIB:

 I will create a 1.7.0 branch off develop in our git repository
 at https://github.com/apache/fineract on Monday, April 25,
 2022.

 The release tracking umbrella issue for tracking all 

Re: [FINERACT] [PROPOSAL]  New release 1.7.0

[Arnold Galovics]

Hi Hitesh,

Thanks for the diligence, we appreciate it.
I'm already working on a solution that's more widespread to the problem and
will avoid future issues like this because there are a couple other places
too where I see the same issue.

Best,
Arnold

On Thu, May 5, 2022 at 9:05 AM hitesh prajapati <
hitesh.kams.prajap...@gmail.com> wrote:

> Hi Aleks, Arnold,
>
> I can raise the PR for the issue which I fixed
> for ReportWritePlatformServiceImpl as described in my previous email if
> that helps.
>
> Thanks,
> Hitesh
>
> On Thu, May 5, 2022 at 12:17 PM hitesh prajapati <
> hitesh.kams.prajap...@gmail.com> wrote:
>
>> Hi Aleks, Arnold,
>>
>> I did encounter similar issue where the below INSERT SQL  failed for the
>> below call because grouping is a keyword in MySQL 8.
>> So I changed this particular call from repository to jdbc template.
>>
>> permissionRepository.save(permission) call from public interface 
>> PermissionRepository
>> extends JpaRepository
>>
>> INSERT INTO m_permission (action_name, can_maker_checker, code, entity_name, 
>> grouping)
>> VALUES ('READ', 0, 'READ_Mifos Balance and Transactions Report', 'Mifos 
>> Balance and Transactions Report',
>> 'report')
>>
>>
>>
>> On Thu, May 5, 2022 at 4:43 AM Aleksandar Vidakovic <
>> chee...@monkeysintown.com> wrote:
>>
>>> Hi everyone,
>>>
>>> ... just wanted to inform everyone about the upcoming release. We'll
>>> probably need another day or so until I'll open the release branch. We had
>>> some reports of SQL syntax errors on certain MySQL instances (Arnold is
>>> working on that) and at the moment there's a sneaky build issue in the
>>> develop branch that I'm trying to fix.
>>>
>>> If we solve these issues in the predicted time frame then we are still
>>> on target with the May 10 release date (more or less).
>>>
>>> Just FYI.
>>>
>>> Cheers,
>>>
>>> Aleks
>>>
>>> On Wed, Apr 27, 2022 at 4:31 PM Aleksandar Vidakovic <
>>> chee...@monkeysintown.com> wrote:
>>>
 Hi everyone,

 ... friendly reminder that we have an upcoming release. I am going to
 open a release branch probably tomorrow. Until then please cleanup your
 tickets for this release. I will start triaging the tickets today and
 tomorrow and move everything that's not finished to the next release.

 Please reach out to me if you have any questions or concerns.

 FYI

 Cheers,

 Aleks

 On Thu, Apr 21, 2022 at 12:22 AM Aleksandar Vidakovic <
 chee...@monkeysintown.com> wrote:

> ... great... the current list of tickets is not too long (not too
> short either)... 65... plenty of room to add... and some of the issues 
> that
> are currently included will move to the next release (mostly stale stuff)
> very likely... so, no problem.
>
> On Thu, Apr 21, 2022 at 12:12 AM Ed Cable  wrote:
>
>> Aleks,
>>
>> I will check with Manoj and Avik from Fynarfin to see if there are
>> any changes that are being worked on that might be ready for inclusion 
>> into
>> 1.7.
>>
>> Ed
>>
>> On Wed, Apr 20, 2022 at 2:34 PM Aleksandar Vidakovic <
>> chee...@monkeysintown.com> wrote:
>>
>>> @Victor Manuel Romero Rodriguez  your
>>> three tickets are included... FYI
>>>
>>> On Wed, Apr 20, 2022 at 11:27 PM Aleksandar Vidakovic <
>>> chee...@monkeysintown.com> wrote:
>>>
 @Victor Manuel Romero Rodriguez  ...
 no problem, I'll add them right now

 On Wed, Apr 20, 2022 at 11:19 PM VICTOR MANUEL ROMERO RODRIGUEZ <
 victor.rom...@fintecheando.mx> wrote:

> Hello Aleks,
>
> Is it possible to include these PRs?
>
> FINERACT-1577 TLS support in fully managed serverless environments
> FINERACT-1576 GCP Cloud SQL Support
> FINERACT-1575 IPv6 workaround
>
> Regards
>
> El mié, 20 abr 2022 a las 16:17, Ed Cable ()
> escribió:
>
>> Thank you Aleks and glad to see all of the automation that you
>> have added to the release process.
>>
>> Ed
>>
>> On Wed, Apr 20, 2022, 14:11 Aleksandar Vidakovic <
>> al...@apache.org> wrote:
>>
>>> Hello everyone,
>>>
>>> Based on our "How to Release Apache Fineract" process documented
>>> at https://cwiki.apache.org/confluence/x/DRwIB:
>>>
>>> I will create a 1.7.0 branch off develop in our git repository
>>> at https://github.com/apache/fineract on Monday, April 25, 2022.
>>>
>>> The release tracking umbrella issue for tracking all activity in
>>> JIRA is FINERACT-1590 (
>>> https://issues.apache.org/jira/browse/FINERACT-1590) for this
>>> Fineract 1.7.0.
>>>
>>> If you have any work in progress that you would like to see
>>> included in this release, please add "blocking" links to the 

Re: [FINERACT] [PROPOSAL]  New release 1.7.0

[hitesh prajapati]

Hi Aleks, Arnold,

I can raise the PR for the issue which I fixed
for ReportWritePlatformServiceImpl as described in my previous email if
that helps.

Thanks,
Hitesh

On Thu, May 5, 2022 at 12:17 PM hitesh prajapati <
hitesh.kams.prajap...@gmail.com> wrote:

> Hi Aleks, Arnold,
>
> I did encounter similar issue where the below INSERT SQL  failed for the
> below call because grouping is a keyword in MySQL 8.
> So I changed this particular call from repository to jdbc template.
>
> permissionRepository.save(permission) call from public interface 
> PermissionRepository
> extends JpaRepository
>
> INSERT INTO m_permission (action_name, can_maker_checker, code, entity_name, 
> grouping)
> VALUES ('READ', 0, 'READ_Mifos Balance and Transactions Report', 'Mifos 
> Balance and Transactions Report',
> 'report')
>
>
>
> On Thu, May 5, 2022 at 4:43 AM Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> Hi everyone,
>>
>> ... just wanted to inform everyone about the upcoming release. We'll
>> probably need another day or so until I'll open the release branch. We had
>> some reports of SQL syntax errors on certain MySQL instances (Arnold is
>> working on that) and at the moment there's a sneaky build issue in the
>> develop branch that I'm trying to fix.
>>
>> If we solve these issues in the predicted time frame then we are still on
>> target with the May 10 release date (more or less).
>>
>> Just FYI.
>>
>> Cheers,
>>
>> Aleks
>>
>> On Wed, Apr 27, 2022 at 4:31 PM Aleksandar Vidakovic <
>> chee...@monkeysintown.com> wrote:
>>
>>> Hi everyone,
>>>
>>> ... friendly reminder that we have an upcoming release. I am going to
>>> open a release branch probably tomorrow. Until then please cleanup your
>>> tickets for this release. I will start triaging the tickets today and
>>> tomorrow and move everything that's not finished to the next release.
>>>
>>> Please reach out to me if you have any questions or concerns.
>>>
>>> FYI
>>>
>>> Cheers,
>>>
>>> Aleks
>>>
>>> On Thu, Apr 21, 2022 at 12:22 AM Aleksandar Vidakovic <
>>> chee...@monkeysintown.com> wrote:
>>>
 ... great... the current list of tickets is not too long (not too short
 either)... 65... plenty of room to add... and some of the issues that are
 currently included will move to the next release (mostly stale stuff) very
 likely... so, no problem.

 On Thu, Apr 21, 2022 at 12:12 AM Ed Cable  wrote:

> Aleks,
>
> I will check with Manoj and Avik from Fynarfin to see if there are any
> changes that are being worked on that might be ready for inclusion into 
> 1.7.
>
> Ed
>
> On Wed, Apr 20, 2022 at 2:34 PM Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> @Victor Manuel Romero Rodriguez  your
>> three tickets are included... FYI
>>
>> On Wed, Apr 20, 2022 at 11:27 PM Aleksandar Vidakovic <
>> chee...@monkeysintown.com> wrote:
>>
>>> @Victor Manuel Romero Rodriguez  ...
>>> no problem, I'll add them right now
>>>
>>> On Wed, Apr 20, 2022 at 11:19 PM VICTOR MANUEL ROMERO RODRIGUEZ <
>>> victor.rom...@fintecheando.mx> wrote:
>>>
 Hello Aleks,

 Is it possible to include these PRs?

 FINERACT-1577 TLS support in fully managed serverless environments
 FINERACT-1576 GCP Cloud SQL Support
 FINERACT-1575 IPv6 workaround

 Regards

 El mié, 20 abr 2022 a las 16:17, Ed Cable ()
 escribió:

> Thank you Aleks and glad to see all of the automation that you
> have added to the release process.
>
> Ed
>
> On Wed, Apr 20, 2022, 14:11 Aleksandar Vidakovic 
> wrote:
>
>> Hello everyone,
>>
>> Based on our "How to Release Apache Fineract" process documented
>> at https://cwiki.apache.org/confluence/x/DRwIB:
>>
>> I will create a 1.7.0 branch off develop in our git repository at
>> https://github.com/apache/fineract on Monday, April 25, 2022.
>>
>> The release tracking umbrella issue for tracking all activity in
>> JIRA is FINERACT-1590 (
>> https://issues.apache.org/jira/browse/FINERACT-1590) for this
>> Fineract 1.7.0.
>>
>> 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,
>>
>> Aleksandar Vidakovic
>>
>>
>>
>>  Powered by Fineract Release Plugin 
>>
>
>
> --
> *Ed Cable*
> President/CEO, Mifos Initiative
> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>
> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>   

Re: [FINERACT] [PROPOSAL]  New release 1.7.0

[hitesh prajapati]

Hi Aleks, Arnold,

I did encounter similar issue where the below INSERT SQL  failed for the
below call because grouping is a keyword in MySQL 8.
So I changed this particular call from repository to jdbc template.

permissionRepository.save(permission) call from public interface
PermissionRepository
extends JpaRepository

INSERT INTO m_permission (action_name, can_maker_checker, code,
entity_name, grouping)
VALUES ('READ', 0, 'READ_Mifos Balance and Transactions Report',
'Mifos Balance and Transactions Report',
'report')



On Thu, May 5, 2022 at 4:43 AM Aleksandar Vidakovic <
chee...@monkeysintown.com> wrote:

> Hi everyone,
>
> ... just wanted to inform everyone about the upcoming release. We'll
> probably need another day or so until I'll open the release branch. We had
> some reports of SQL syntax errors on certain MySQL instances (Arnold is
> working on that) and at the moment there's a sneaky build issue in the
> develop branch that I'm trying to fix.
>
> If we solve these issues in the predicted time frame then we are still on
> target with the May 10 release date (more or less).
>
> Just FYI.
>
> Cheers,
>
> Aleks
>
> On Wed, Apr 27, 2022 at 4:31 PM Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> Hi everyone,
>>
>> ... friendly reminder that we have an upcoming release. I am going to
>> open a release branch probably tomorrow. Until then please cleanup your
>> tickets for this release. I will start triaging the tickets today and
>> tomorrow and move everything that's not finished to the next release.
>>
>> Please reach out to me if you have any questions or concerns.
>>
>> FYI
>>
>> Cheers,
>>
>> Aleks
>>
>> On Thu, Apr 21, 2022 at 12:22 AM Aleksandar Vidakovic <
>> chee...@monkeysintown.com> wrote:
>>
>>> ... great... the current list of tickets is not too long (not too short
>>> either)... 65... plenty of room to add... and some of the issues that are
>>> currently included will move to the next release (mostly stale stuff) very
>>> likely... so, no problem.
>>>
>>> On Thu, Apr 21, 2022 at 12:12 AM Ed Cable  wrote:
>>>
 Aleks,

 I will check with Manoj and Avik from Fynarfin to see if there are any
 changes that are being worked on that might be ready for inclusion into 
 1.7.

 Ed

 On Wed, Apr 20, 2022 at 2:34 PM Aleksandar Vidakovic <
 chee...@monkeysintown.com> wrote:

> @Victor Manuel Romero Rodriguez  your
> three tickets are included... FYI
>
> On Wed, Apr 20, 2022 at 11:27 PM Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> @Victor Manuel Romero Rodriguez  ...
>> no problem, I'll add them right now
>>
>> On Wed, Apr 20, 2022 at 11:19 PM VICTOR MANUEL ROMERO RODRIGUEZ <
>> victor.rom...@fintecheando.mx> wrote:
>>
>>> Hello Aleks,
>>>
>>> Is it possible to include these PRs?
>>>
>>> FINERACT-1577 TLS support in fully managed serverless environments
>>> FINERACT-1576 GCP Cloud SQL Support
>>> FINERACT-1575 IPv6 workaround
>>>
>>> Regards
>>>
>>> El mié, 20 abr 2022 a las 16:17, Ed Cable ()
>>> escribió:
>>>
 Thank you Aleks and glad to see all of the automation that you have
 added to the release process.

 Ed

 On Wed, Apr 20, 2022, 14:11 Aleksandar Vidakovic 
 wrote:

> Hello everyone,
>
> Based on our "How to Release Apache Fineract" process documented
> at https://cwiki.apache.org/confluence/x/DRwIB:
>
> I will create a 1.7.0 branch off develop in our git repository at
> https://github.com/apache/fineract on Monday, April 25, 2022.
>
> The release tracking umbrella issue for tracking all activity in
> JIRA is FINERACT-1590 (
> https://issues.apache.org/jira/browse/FINERACT-1590) for this
> Fineract 1.7.0.
>
> 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,
>
> Aleksandar Vidakovic
>
>
>
>  Powered by Fineract Release Plugin 
>


 --
 *Ed Cable*
 President/CEO, Mifos Initiative
 edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649

 *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
   

Re: [FINERACT] [PROPOSAL]  New release 1.7.0

[Aleksandar Vidakovic]

Hi everyone,

... just wanted to inform everyone about the upcoming release. We'll
probably need another day or so until I'll open the release branch. We had
some reports of SQL syntax errors on certain MySQL instances (Arnold is
working on that) and at the moment there's a sneaky build issue in the
develop branch that I'm trying to fix.

If we solve these issues in the predicted time frame then we are still on
target with the May 10 release date (more or less).

Just FYI.

Cheers,

Aleks

On Wed, Apr 27, 2022 at 4:31 PM Aleksandar Vidakovic <
chee...@monkeysintown.com> wrote:

> Hi everyone,
>
> ... friendly reminder that we have an upcoming release. I am going to open
> a release branch probably tomorrow. Until then please cleanup your tickets
> for this release. I will start triaging the tickets today and tomorrow and
> move everything that's not finished to the next release.
>
> Please reach out to me if you have any questions or concerns.
>
> FYI
>
> Cheers,
>
> Aleks
>
> On Thu, Apr 21, 2022 at 12:22 AM Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> ... great... the current list of tickets is not too long (not too short
>> either)... 65... plenty of room to add... and some of the issues that are
>> currently included will move to the next release (mostly stale stuff) very
>> likely... so, no problem.
>>
>> On Thu, Apr 21, 2022 at 12:12 AM Ed Cable  wrote:
>>
>>> Aleks,
>>>
>>> I will check with Manoj and Avik from Fynarfin to see if there are any
>>> changes that are being worked on that might be ready for inclusion into 1.7.
>>>
>>> Ed
>>>
>>> On Wed, Apr 20, 2022 at 2:34 PM Aleksandar Vidakovic <
>>> chee...@monkeysintown.com> wrote:
>>>
 @Victor Manuel Romero Rodriguez  your
 three tickets are included... FYI

 On Wed, Apr 20, 2022 at 11:27 PM Aleksandar Vidakovic <
 chee...@monkeysintown.com> wrote:

> @Victor Manuel Romero Rodriguez  ...
> no problem, I'll add them right now
>
> On Wed, Apr 20, 2022 at 11:19 PM VICTOR MANUEL ROMERO RODRIGUEZ <
> victor.rom...@fintecheando.mx> wrote:
>
>> Hello Aleks,
>>
>> Is it possible to include these PRs?
>>
>> FINERACT-1577 TLS support in fully managed serverless environments
>> FINERACT-1576 GCP Cloud SQL Support
>> FINERACT-1575 IPv6 workaround
>>
>> Regards
>>
>> El mié, 20 abr 2022 a las 16:17, Ed Cable ()
>> escribió:
>>
>>> Thank you Aleks and glad to see all of the automation that you have
>>> added to the release process.
>>>
>>> Ed
>>>
>>> On Wed, Apr 20, 2022, 14:11 Aleksandar Vidakovic 
>>> wrote:
>>>
 Hello everyone,

 Based on our "How to Release Apache Fineract" process documented at
 https://cwiki.apache.org/confluence/x/DRwIB:

 I will create a 1.7.0 branch off develop in our git repository at
 https://github.com/apache/fineract on Monday, April 25, 2022.

 The release tracking umbrella issue for tracking all activity in
 JIRA is FINERACT-1590 (
 https://issues.apache.org/jira/browse/FINERACT-1590) for this
 Fineract 1.7.0.

 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,

 Aleksandar Vidakovic



  Powered by Fineract Release Plugin 

>>>
>>>
>>> --
>>> *Ed Cable*
>>> President/CEO, Mifos Initiative
>>> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>>>
>>> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>>>   
>>>
>>>

Re: [FINERACT] [PROPOSAL]  New release 1.7.0

[Aleksandar Vidakovic]

Hi everyone,

... friendly reminder that we have an upcoming release. I am going to open
a release branch probably tomorrow. Until then please cleanup your tickets
for this release. I will start triaging the tickets today and tomorrow and
move everything that's not finished to the next release.

Please reach out to me if you have any questions or concerns.

FYI

Cheers,

Aleks

On Thu, Apr 21, 2022 at 12:22 AM Aleksandar Vidakovic <
chee...@monkeysintown.com> wrote:

> ... great... the current list of tickets is not too long (not too short
> either)... 65... plenty of room to add... and some of the issues that are
> currently included will move to the next release (mostly stale stuff) very
> likely... so, no problem.
>
> On Thu, Apr 21, 2022 at 12:12 AM Ed Cable  wrote:
>
>> Aleks,
>>
>> I will check with Manoj and Avik from Fynarfin to see if there are any
>> changes that are being worked on that might be ready for inclusion into 1.7.
>>
>> Ed
>>
>> On Wed, Apr 20, 2022 at 2:34 PM Aleksandar Vidakovic <
>> chee...@monkeysintown.com> wrote:
>>
>>> @Victor Manuel Romero Rodriguez  your
>>> three tickets are included... FYI
>>>
>>> On Wed, Apr 20, 2022 at 11:27 PM Aleksandar Vidakovic <
>>> chee...@monkeysintown.com> wrote:
>>>
 @Victor Manuel Romero Rodriguez  ... no
 problem, I'll add them right now

 On Wed, Apr 20, 2022 at 11:19 PM VICTOR MANUEL ROMERO RODRIGUEZ <
 victor.rom...@fintecheando.mx> wrote:

> Hello Aleks,
>
> Is it possible to include these PRs?
>
> FINERACT-1577 TLS support in fully managed serverless environments
> FINERACT-1576 GCP Cloud SQL Support
> FINERACT-1575 IPv6 workaround
>
> Regards
>
> El mié, 20 abr 2022 a las 16:17, Ed Cable ()
> escribió:
>
>> Thank you Aleks and glad to see all of the automation that you have
>> added to the release process.
>>
>> Ed
>>
>> On Wed, Apr 20, 2022, 14:11 Aleksandar Vidakovic 
>> wrote:
>>
>>> Hello everyone,
>>>
>>> Based on our "How to Release Apache Fineract" process documented at
>>> https://cwiki.apache.org/confluence/x/DRwIB:
>>>
>>> I will create a 1.7.0 branch off develop in our git repository at
>>> https://github.com/apache/fineract on Monday, April 25, 2022.
>>>
>>> The release tracking umbrella issue for tracking all activity in
>>> JIRA is FINERACT-1590 (
>>> https://issues.apache.org/jira/browse/FINERACT-1590) for this
>>> Fineract 1.7.0.
>>>
>>> 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,
>>>
>>> Aleksandar Vidakovic
>>>
>>>
>>>
>>>  Powered by Fineract Release Plugin 
>>>
>>
>>
>> --
>> *Ed Cable*
>> President/CEO, Mifos Initiative
>> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>>
>> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>>   
>>
>>

Re: [FINERACT] [PROPOSAL]  New release 1.7.0

[Aleksandar Vidakovic]

... great... the current list of tickets is not too long (not too short
either)... 65... plenty of room to add... and some of the issues that are
currently included will move to the next release (mostly stale stuff) very
likely... so, no problem.

On Thu, Apr 21, 2022 at 12:12 AM Ed Cable  wrote:

> Aleks,
>
> I will check with Manoj and Avik from Fynarfin to see if there are any
> changes that are being worked on that might be ready for inclusion into 1.7.
>
> Ed
>
> On Wed, Apr 20, 2022 at 2:34 PM Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> @Victor Manuel Romero Rodriguez  your
>> three tickets are included... FYI
>>
>> On Wed, Apr 20, 2022 at 11:27 PM Aleksandar Vidakovic <
>> chee...@monkeysintown.com> wrote:
>>
>>> @Victor Manuel Romero Rodriguez  ... no
>>> problem, I'll add them right now
>>>
>>> On Wed, Apr 20, 2022 at 11:19 PM VICTOR MANUEL ROMERO RODRIGUEZ <
>>> victor.rom...@fintecheando.mx> wrote:
>>>
 Hello Aleks,

 Is it possible to include these PRs?

 FINERACT-1577 TLS support in fully managed serverless environments
 FINERACT-1576 GCP Cloud SQL Support
 FINERACT-1575 IPv6 workaround

 Regards

 El mié, 20 abr 2022 a las 16:17, Ed Cable ()
 escribió:

> Thank you Aleks and glad to see all of the automation that you have
> added to the release process.
>
> Ed
>
> On Wed, Apr 20, 2022, 14:11 Aleksandar Vidakovic 
> wrote:
>
>> Hello everyone,
>>
>> Based on our "How to Release Apache Fineract" process documented at
>> https://cwiki.apache.org/confluence/x/DRwIB:
>>
>> I will create a 1.7.0 branch off develop in our git repository at
>> https://github.com/apache/fineract on Monday, April 25, 2022.
>>
>> The release tracking umbrella issue for tracking all activity in JIRA
>> is FINERACT-1590 (https://issues.apache.org/jira/browse/FINERACT-1590)
>> for this Fineract 1.7.0.
>>
>> 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,
>>
>> Aleksandar Vidakovic
>>
>>
>>
>>  Powered by Fineract Release Plugin 
>>
>
>
> --
> *Ed Cable*
> President/CEO, Mifos Initiative
> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>
> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>   
>
>

Re: [FINERACT] [PROPOSAL]  New release 1.7.0

[Ed Cable]

Aleks,

I will check with Manoj and Avik from Fynarfin to see if there are any
changes that are being worked on that might be ready for inclusion into 1.7.

Ed

On Wed, Apr 20, 2022 at 2:34 PM Aleksandar Vidakovic <
chee...@monkeysintown.com> wrote:

> @Victor Manuel Romero Rodriguez  your
> three tickets are included... FYI
>
> On Wed, Apr 20, 2022 at 11:27 PM Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> @Victor Manuel Romero Rodriguez  ... no
>> problem, I'll add them right now
>>
>> On Wed, Apr 20, 2022 at 11:19 PM VICTOR MANUEL ROMERO RODRIGUEZ <
>> victor.rom...@fintecheando.mx> wrote:
>>
>>> Hello Aleks,
>>>
>>> Is it possible to include these PRs?
>>>
>>> FINERACT-1577 TLS support in fully managed serverless environments
>>> FINERACT-1576 GCP Cloud SQL Support
>>> FINERACT-1575 IPv6 workaround
>>>
>>> Regards
>>>
>>> El mié, 20 abr 2022 a las 16:17, Ed Cable ()
>>> escribió:
>>>
 Thank you Aleks and glad to see all of the automation that you have
 added to the release process.

 Ed

 On Wed, Apr 20, 2022, 14:11 Aleksandar Vidakovic 
 wrote:

> Hello everyone,
>
> Based on our "How to Release Apache Fineract" process documented at
> https://cwiki.apache.org/confluence/x/DRwIB:
>
> I will create a 1.7.0 branch off develop in our git repository at
> https://github.com/apache/fineract on Monday, April 25, 2022.
>
> The release tracking umbrella issue for tracking all activity in JIRA
> is FINERACT-1590 (https://issues.apache.org/jira/browse/FINERACT-1590)
> for this Fineract 1.7.0.
>
> 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,
>
> Aleksandar Vidakovic
>
>
>
>  Powered by Fineract Release Plugin 
>


-- 
*Ed Cable*
President/CEO, Mifos Initiative
edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649

*Collectively Creating a World of 3 Billion Maries | *http://mifos.org
  

Re: [FINERACT] [PROPOSAL]  New release 1.7.0

[Aleksandar Vidakovic]

@Victor Manuel Romero Rodriguez  your three
tickets are included... FYI

On Wed, Apr 20, 2022 at 11:27 PM Aleksandar Vidakovic <
chee...@monkeysintown.com> wrote:

> @Victor Manuel Romero Rodriguez  ... no
> problem, I'll add them right now
>
> On Wed, Apr 20, 2022 at 11:19 PM VICTOR MANUEL ROMERO RODRIGUEZ <
> victor.rom...@fintecheando.mx> wrote:
>
>> Hello Aleks,
>>
>> Is it possible to include these PRs?
>>
>> FINERACT-1577 TLS support in fully managed serverless environments
>> FINERACT-1576 GCP Cloud SQL Support
>> FINERACT-1575 IPv6 workaround
>>
>> Regards
>>
>> El mié, 20 abr 2022 a las 16:17, Ed Cable () escribió:
>>
>>> Thank you Aleks and glad to see all of the automation that you have
>>> added to the release process.
>>>
>>> Ed
>>>
>>> On Wed, Apr 20, 2022, 14:11 Aleksandar Vidakovic 
>>> wrote:
>>>
 Hello everyone,

 Based on our "How to Release Apache Fineract" process documented at
 https://cwiki.apache.org/confluence/x/DRwIB:

 I will create a 1.7.0 branch off develop in our git repository at
 https://github.com/apache/fineract on Monday, April 25, 2022.

 The release tracking umbrella issue for tracking all activity in JIRA
 is FINERACT-1590 (https://issues.apache.org/jira/browse/FINERACT-1590)
 for this Fineract 1.7.0.

 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,

 Aleksandar Vidakovic



  Powered by Fineract Release Plugin 

>>>

Re: [FINERACT] [PROPOSAL]  New release 1.7.0

[Aleksandar Vidakovic]

@Victor Manuel Romero Rodriguez  ... no
problem, I'll add them right now

On Wed, Apr 20, 2022 at 11:19 PM VICTOR MANUEL ROMERO RODRIGUEZ <
victor.rom...@fintecheando.mx> wrote:

> Hello Aleks,
>
> Is it possible to include these PRs?
>
> FINERACT-1577 TLS support in fully managed serverless environments
> FINERACT-1576 GCP Cloud SQL Support
> FINERACT-1575 IPv6 workaround
>
> Regards
>
> El mié, 20 abr 2022 a las 16:17, Ed Cable () escribió:
>
>> Thank you Aleks and glad to see all of the automation that you have added
>> to the release process.
>>
>> Ed
>>
>> On Wed, Apr 20, 2022, 14:11 Aleksandar Vidakovic 
>> wrote:
>>
>>> Hello everyone,
>>>
>>> Based on our "How to Release Apache Fineract" process documented at
>>> https://cwiki.apache.org/confluence/x/DRwIB:
>>>
>>> I will create a 1.7.0 branch off develop in our git repository at
>>> https://github.com/apache/fineract on Monday, April 25, 2022.
>>>
>>> The release tracking umbrella issue for tracking all activity in JIRA is
>>> FINERACT-1590 (https://issues.apache.org/jira/browse/FINERACT-1590) for
>>> this Fineract 1.7.0.
>>>
>>> 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,
>>>
>>> Aleksandar Vidakovic
>>>
>>>
>>>
>>>  Powered by Fineract Release Plugin 
>>>
>>

Re: [FINERACT] [PROPOSAL]  New release 1.7.0

[VICTOR MANUEL ROMERO RODRIGUEZ]

Hello Aleks,

Is it possible to include these PRs?

FINERACT-1577 TLS support in fully managed serverless environments
FINERACT-1576 GCP Cloud SQL Support
FINERACT-1575 IPv6 workaround

Regards

El mié, 20 abr 2022 a las 16:17, Ed Cable () escribió:

> Thank you Aleks and glad to see all of the automation that you have added
> to the release process.
>
> Ed
>
> On Wed, Apr 20, 2022, 14:11 Aleksandar Vidakovic  wrote:
>
>> Hello everyone,
>>
>> Based on our "How to Release Apache Fineract" process documented at
>> https://cwiki.apache.org/confluence/x/DRwIB:
>>
>> I will create a 1.7.0 branch off develop in our git repository at
>> https://github.com/apache/fineract on Monday, April 25, 2022.
>>
>> The release tracking umbrella issue for tracking all activity in JIRA is
>> FINERACT-1590 (https://issues.apache.org/jira/browse/FINERACT-1590) for
>> this Fineract 1.7.0.
>>
>> 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,
>>
>> Aleksandar Vidakovic
>>
>>
>>
>>  Powered by Fineract Release Plugin 
>>
>

Re: [FINERACT] [PROPOSAL]  New release 1.7.0

[Ed Cable]

Thank you Aleks and glad to see all of the automation that you have added
to the release process.

Ed

On Wed, Apr 20, 2022, 14:11 Aleksandar Vidakovic  wrote:

> Hello everyone,
>
> Based on our "How to Release Apache Fineract" process documented at
> https://cwiki.apache.org/confluence/x/DRwIB:
>
> I will create a 1.7.0 branch off develop in our git repository at
> https://github.com/apache/fineract on Monday, April 25, 2022.
>
> The release tracking umbrella issue for tracking all activity in JIRA is
> FINERACT-1590 (https://issues.apache.org/jira/browse/FINERACT-1590) for
> this Fineract 1.7.0.
>
> 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,
>
> Aleksandar Vidakovic
>
>
>
>  Powered by Fineract Release Plugin 
>