You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@fineract.apache.org by Aleksandar Vidakovic <ch...@monkeysintown.com> on 2022/02/03 18:12:03 UTC
Let's have a new release (1.6.0)...
Hi everyone,
... it has been a while since our last 1.5.0 release, and since then we've
added and updated quite a bit. Among the usual fixes and improvements we
have major dependency upgrades (Spring, Spring Boot, Jersey) and got rid of
Spring XML configuration while still maintaining 100% backwards
compatibility. I think these changes are worth a new release, so I'm
proposing to have a 1.6.0 release soon (in February) before this gets too
big.
It would be great if you could all have a look at Jira and either fix/close
the tickets associated with version 1.6 and add anything that really needs
to go into this release. Keep in mind that we'll have other patch (1.6.1,
1.6.2...) and minor releases (1.7.0....). Would be great if we can move
tickets that are not essential to a later release... just to get 1.6 out
without too much of a delay.
Please see here for the tickets currently associated with version 1.6:
https://issues.apache.org/jira/browse/FINERACT-1482?jql=project%20%3D%20%22Apache%20Fineract%22%20AND%20resolution%20is%20EMPTY%20and%20fixVersion%20%3D%201.6.0%20%20ORDER%20by%20status%20DESC%2C%20priority%20DESC%2C%20updated%20DESC
If there are no objections I'd open the 1.6.0 release branch soon (at the
latest on Monday). If you need any help then please let me know.
Cheers,
Aleks
Re: Let's have a new release (1.6.0)...
Posted by Petri Tuomola <pe...@tuomola.org.INVALID>.
Hi Aleks - fully support going ahead with the release, in fact I had been
thinking this would be a good idea given a lot of major changes that have
gone in since 1.5.
Cheers
Petri
On Fri, Feb 11, 2022, 05:40 Aleksandar Vidakovic <ch...@monkeysintown.com>
wrote:
> Hello everyone,
>
> ... just wanted to check-in on our planned release... can I assume that
> the silence means we can go ahead and open a release branch?
>
> There was not much movement concerning the Jira tickets... if there are no
> objections I would move the remaining tickets (see screenshot in my
> previous email) to the next release so that we can move on and have a
> proper release without too much delay. From my perspective I don't see
> anything in that list that would be a show stopper.
>
> Let me know.
>
> Cheers,
>
> Aleks
>
> On Sun, Feb 6, 2022 at 3:22 AM Aleksandar Vidakovic <
> cheetah@monkeysintown.com> wrote:
>
>> Hi everyone,
>>
>> ... I did a bit of housekeeping... these are the currently open issues
>> for 1.6.0:
>>
>> [image: image.png]
>>
>> Note: I have moved all open and unassigned issues to a later version
>> (1.8.0). Please have a look at it and feel free to move issues to 1.6.0 if
>> you think they are necessary. Keep in mind that these issues are very old
>> and we did already 2 releases (1.4.0 and 1.5.0) without them; if you move
>> an issue to 1.6.0 then please assign it to you or someone who's willing to
>> fix it; just moving without any assignment doesn't make a lot of sense.
>>
>> Above list contains 23 issues; some almost done:
>>
>> - FINERACT-1446: just waiting for PR approvals and merges for 2
>> sub-tasks (improved Hikari/connection pool and SSL configuration)
>> - FINERACT-1482: just need the Docker Hub credentials configured;
>> pushing Docker images is then simple (needs a Github Action configured and
>> executing a different Gradle Jib task)
>> - FINERACT-1496: just needs a bit of formatting with "spotlessApply"
>> and is otherwise ready for merging
>>
>> Would be great if you could help out to ideally attack the open issues
>> and finish any ongoing work for this release. In case we don't find enough
>> people to solve these issues I'll concentrate on BLOCKER and CRITICAL; this
>> would narrow down our list to approx. 5 issues. Before we do that let's see
>> how many of those open issues we can close.
>>
>> Thanks and please let me know if you need any help.
>>
>> Cheers,
>>
>> Aleks
>>
>>
>> On Thu, Feb 3, 2022 at 9:51 PM Aleksandar Vidakovic <
>> cheetah@monkeysintown.com> wrote:
>>
>>> ... I'll get the handful that are associated with me out of the way over
>>> the weekend... non of them are critical, more convenience stuff (like
>>> easier releases)... can be all pushed to later... one PR concerning
>>> simplifying DB configuration is almost ready... and another one that is
>>> basically just a reminder will be closed (was too big of a change, I split
>>> it up in smaller PRs that are already merged).
>>>
>>> ... and as James said: if you need any help then just let me know.
>>>
>>>
>>> On Thu, Feb 3, 2022 at 8:17 PM James Dailey <ja...@gmail.com>
>>> wrote:
>>>
>>>> Alexandar - Let me know if I can help with the process, and great to
>>>> see this underway.
>>>> Regular and frequent releases are important.
>>>>
>>>> If helpful, you can also see the Kanban Board for release 1.6 :
>>>> https://issues.apache.org/jira/projects/FINERACT/versions/12349949
>>>>
>>>> I started to go through some of the unassigned issues and think we can
>>>> safely remove them from 1.6 as no one has taken them up.
>>>> They can be moved to a 1.6.1 or such.
>>>>
>>>> Of the 13 in progress, it looks like you have a few assigned to
>>>> yourself. ;).
>>>>
>>>> I think it is probably more important to make sure that the 89 resolved
>>>> issues get into a stable release.
>>>> It might mean requiring more work on some of them, so we should perhaps
>>>> only include those that contribute to stability, scalability, and
>>>> maintainability.
>>>>
>>>>
>>>> https://cwiki.apache.org/confluence/display/FINERACT/How+to+Release+Apache+Fineract
>>>>
>>>>
>>>>
>>>>
>>>> On Thu, Feb 3, 2022 at 10:34 AM Ed Cable <ed...@mifos.org> wrote:
>>>>
>>>>> Thanks Aleks for spearheading this process once again. I will try to
>>>>> ping any contributors that have open pull requests at the moment or
>>>>> forthcoming PRs.
>>>>>
>>>>> Ed
>>>>>
>>>>> On Thu, Feb 3, 2022 at 10:12 AM Aleksandar Vidakovic <
>>>>> cheetah@monkeysintown.com> wrote:
>>>>>
>>>>>> Hi everyone,
>>>>>>
>>>>>> ... it has been a while since our last 1.5.0 release, and since then
>>>>>> we've added and updated quite a bit. Among the usual fixes and improvements
>>>>>> we have major dependency upgrades (Spring, Spring Boot, Jersey) and got rid
>>>>>> of Spring XML configuration while still maintaining 100% backwards
>>>>>> compatibility. I think these changes are worth a new release, so I'm
>>>>>> proposing to have a 1.6.0 release soon (in February) before this gets too
>>>>>> big.
>>>>>>
>>>>>> It would be great if you could all have a look at Jira and either
>>>>>> fix/close the tickets associated with version 1.6 and add anything that
>>>>>> really needs to go into this release. Keep in mind that we'll have other
>>>>>> patch (1.6.1, 1.6.2...) and minor releases (1.7.0....). Would be great if
>>>>>> we can move tickets that are not essential to a later release... just to
>>>>>> get 1.6 out without too much of a delay.
>>>>>>
>>>>>> Please see here for the tickets currently associated with version 1.6:
>>>>>>
>>>>>>
>>>>>> https://issues.apache.org/jira/browse/FINERACT-1482?jql=project%20%3D%20%22Apache%20Fineract%22%20AND%20resolution%20is%20EMPTY%20and%20fixVersion%20%3D%201.6.0%20%20ORDER%20by%20status%20DESC%2C%20priority%20DESC%2C%20updated%20DESC
>>>>>>
>>>>>> If there are no objections I'd open the 1.6.0 release branch soon (at
>>>>>> the latest on Monday). If you need any help then please let me know.
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Aleks
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Ed Cable*
>>>>> President/CEO, Mifos Initiative
>>>>> edcable@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>>>>>
>>>>> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>>>>> <http://facebook.com/mifos> <http://www.twitter.com/mifos>
>>>>>
>>>>>
Re: Let's have a new release (1.6.0)...
Posted by Aleksandar Vidakovic <ch...@monkeysintown.com>.
Hello everyone,
... just wanted to check-in on our planned release... can I assume that the
silence means we can go ahead and open a release branch?
There was not much movement concerning the Jira tickets... if there are no
objections I would move the remaining tickets (see screenshot in my
previous email) to the next release so that we can move on and have a
proper release without too much delay. From my perspective I don't see
anything in that list that would be a show stopper.
Let me know.
Cheers,
Aleks
On Sun, Feb 6, 2022 at 3:22 AM Aleksandar Vidakovic <
cheetah@monkeysintown.com> wrote:
> Hi everyone,
>
> ... I did a bit of housekeeping... these are the currently open issues for
> 1.6.0:
>
> [image: image.png]
>
> Note: I have moved all open and unassigned issues to a later version
> (1.8.0). Please have a look at it and feel free to move issues to 1.6.0 if
> you think they are necessary. Keep in mind that these issues are very old
> and we did already 2 releases (1.4.0 and 1.5.0) without them; if you move
> an issue to 1.6.0 then please assign it to you or someone who's willing to
> fix it; just moving without any assignment doesn't make a lot of sense.
>
> Above list contains 23 issues; some almost done:
>
> - FINERACT-1446: just waiting for PR approvals and merges for 2
> sub-tasks (improved Hikari/connection pool and SSL configuration)
> - FINERACT-1482: just need the Docker Hub credentials configured;
> pushing Docker images is then simple (needs a Github Action configured and
> executing a different Gradle Jib task)
> - FINERACT-1496: just needs a bit of formatting with "spotlessApply"
> and is otherwise ready for merging
>
> Would be great if you could help out to ideally attack the open issues and
> finish any ongoing work for this release. In case we don't find enough
> people to solve these issues I'll concentrate on BLOCKER and CRITICAL; this
> would narrow down our list to approx. 5 issues. Before we do that let's see
> how many of those open issues we can close.
>
> Thanks and please let me know if you need any help.
>
> Cheers,
>
> Aleks
>
>
> On Thu, Feb 3, 2022 at 9:51 PM Aleksandar Vidakovic <
> cheetah@monkeysintown.com> wrote:
>
>> ... I'll get the handful that are associated with me out of the way over
>> the weekend... non of them are critical, more convenience stuff (like
>> easier releases)... can be all pushed to later... one PR concerning
>> simplifying DB configuration is almost ready... and another one that is
>> basically just a reminder will be closed (was too big of a change, I split
>> it up in smaller PRs that are already merged).
>>
>> ... and as James said: if you need any help then just let me know.
>>
>>
>> On Thu, Feb 3, 2022 at 8:17 PM James Dailey <ja...@gmail.com>
>> wrote:
>>
>>> Alexandar - Let me know if I can help with the process, and great to see
>>> this underway.
>>> Regular and frequent releases are important.
>>>
>>> If helpful, you can also see the Kanban Board for release 1.6 :
>>> https://issues.apache.org/jira/projects/FINERACT/versions/12349949
>>>
>>> I started to go through some of the unassigned issues and think we can
>>> safely remove them from 1.6 as no one has taken them up.
>>> They can be moved to a 1.6.1 or such.
>>>
>>> Of the 13 in progress, it looks like you have a few assigned to
>>> yourself. ;).
>>>
>>> I think it is probably more important to make sure that the 89 resolved
>>> issues get into a stable release.
>>> It might mean requiring more work on some of them, so we should perhaps
>>> only include those that contribute to stability, scalability, and
>>> maintainability.
>>>
>>>
>>> https://cwiki.apache.org/confluence/display/FINERACT/How+to+Release+Apache+Fineract
>>>
>>>
>>>
>>>
>>> On Thu, Feb 3, 2022 at 10:34 AM Ed Cable <ed...@mifos.org> wrote:
>>>
>>>> Thanks Aleks for spearheading this process once again. I will try to
>>>> ping any contributors that have open pull requests at the moment or
>>>> forthcoming PRs.
>>>>
>>>> Ed
>>>>
>>>> On Thu, Feb 3, 2022 at 10:12 AM Aleksandar Vidakovic <
>>>> cheetah@monkeysintown.com> wrote:
>>>>
>>>>> Hi everyone,
>>>>>
>>>>> ... it has been a while since our last 1.5.0 release, and since then
>>>>> we've added and updated quite a bit. Among the usual fixes and improvements
>>>>> we have major dependency upgrades (Spring, Spring Boot, Jersey) and got rid
>>>>> of Spring XML configuration while still maintaining 100% backwards
>>>>> compatibility. I think these changes are worth a new release, so I'm
>>>>> proposing to have a 1.6.0 release soon (in February) before this gets too
>>>>> big.
>>>>>
>>>>> It would be great if you could all have a look at Jira and either
>>>>> fix/close the tickets associated with version 1.6 and add anything that
>>>>> really needs to go into this release. Keep in mind that we'll have other
>>>>> patch (1.6.1, 1.6.2...) and minor releases (1.7.0....). Would be great if
>>>>> we can move tickets that are not essential to a later release... just to
>>>>> get 1.6 out without too much of a delay.
>>>>>
>>>>> Please see here for the tickets currently associated with version 1.6:
>>>>>
>>>>>
>>>>> https://issues.apache.org/jira/browse/FINERACT-1482?jql=project%20%3D%20%22Apache%20Fineract%22%20AND%20resolution%20is%20EMPTY%20and%20fixVersion%20%3D%201.6.0%20%20ORDER%20by%20status%20DESC%2C%20priority%20DESC%2C%20updated%20DESC
>>>>>
>>>>> If there are no objections I'd open the 1.6.0 release branch soon (at
>>>>> the latest on Monday). If you need any help then please let me know.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Aleks
>>>>>
>>>>
>>>>
>>>> --
>>>> *Ed Cable*
>>>> President/CEO, Mifos Initiative
>>>> edcable@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>>>>
>>>> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>>>> <http://facebook.com/mifos> <http://www.twitter.com/mifos>
>>>>
>>>>
Re: Let's have a new release (1.6.0)...
Posted by Aleksandar Vidakovic <ch...@monkeysintown.com>.
Hi everyone,
... I did a bit of housekeeping... these are the currently open issues for
1.6.0:
[image: image.png]
Note: I have moved all open and unassigned issues to a later version
(1.8.0). Please have a look at it and feel free to move issues to 1.6.0 if
you think they are necessary. Keep in mind that these issues are very old
and we did already 2 releases (1.4.0 and 1.5.0) without them; if you move
an issue to 1.6.0 then please assign it to you or someone who's willing to
fix it; just moving without any assignment doesn't make a lot of sense.
Above list contains 23 issues; some almost done:
- FINERACT-1446: just waiting for PR approvals and merges for 2
sub-tasks (improved Hikari/connection pool and SSL configuration)
- FINERACT-1482: just need the Docker Hub credentials configured;
pushing Docker images is then simple (needs a Github Action configured and
executing a different Gradle Jib task)
- FINERACT-1496: just needs a bit of formatting with "spotlessApply" and
is otherwise ready for merging
Would be great if you could help out to ideally attack the open issues and
finish any ongoing work for this release. In case we don't find enough
people to solve these issues I'll concentrate on BLOCKER and CRITICAL; this
would narrow down our list to approx. 5 issues. Before we do that let's see
how many of those open issues we can close.
Thanks and please let me know if you need any help.
Cheers,
Aleks
On Thu, Feb 3, 2022 at 9:51 PM Aleksandar Vidakovic <
cheetah@monkeysintown.com> wrote:
> ... I'll get the handful that are associated with me out of the way over
> the weekend... non of them are critical, more convenience stuff (like
> easier releases)... can be all pushed to later... one PR concerning
> simplifying DB configuration is almost ready... and another one that is
> basically just a reminder will be closed (was too big of a change, I split
> it up in smaller PRs that are already merged).
>
> ... and as James said: if you need any help then just let me know.
>
>
> On Thu, Feb 3, 2022 at 8:17 PM James Dailey <ja...@gmail.com>
> wrote:
>
>> Alexandar - Let me know if I can help with the process, and great to see
>> this underway.
>> Regular and frequent releases are important.
>>
>> If helpful, you can also see the Kanban Board for release 1.6 :
>> https://issues.apache.org/jira/projects/FINERACT/versions/12349949
>>
>> I started to go through some of the unassigned issues and think we can
>> safely remove them from 1.6 as no one has taken them up.
>> They can be moved to a 1.6.1 or such.
>>
>> Of the 13 in progress, it looks like you have a few assigned to yourself.
>> ;).
>>
>> I think it is probably more important to make sure that the 89 resolved
>> issues get into a stable release.
>> It might mean requiring more work on some of them, so we should perhaps
>> only include those that contribute to stability, scalability, and
>> maintainability.
>>
>>
>> https://cwiki.apache.org/confluence/display/FINERACT/How+to+Release+Apache+Fineract
>>
>>
>>
>>
>> On Thu, Feb 3, 2022 at 10:34 AM Ed Cable <ed...@mifos.org> wrote:
>>
>>> Thanks Aleks for spearheading this process once again. I will try to
>>> ping any contributors that have open pull requests at the moment or
>>> forthcoming PRs.
>>>
>>> Ed
>>>
>>> On Thu, Feb 3, 2022 at 10:12 AM Aleksandar Vidakovic <
>>> cheetah@monkeysintown.com> wrote:
>>>
>>>> Hi everyone,
>>>>
>>>> ... it has been a while since our last 1.5.0 release, and since then
>>>> we've added and updated quite a bit. Among the usual fixes and improvements
>>>> we have major dependency upgrades (Spring, Spring Boot, Jersey) and got rid
>>>> of Spring XML configuration while still maintaining 100% backwards
>>>> compatibility. I think these changes are worth a new release, so I'm
>>>> proposing to have a 1.6.0 release soon (in February) before this gets too
>>>> big.
>>>>
>>>> It would be great if you could all have a look at Jira and either
>>>> fix/close the tickets associated with version 1.6 and add anything that
>>>> really needs to go into this release. Keep in mind that we'll have other
>>>> patch (1.6.1, 1.6.2...) and minor releases (1.7.0....). Would be great if
>>>> we can move tickets that are not essential to a later release... just to
>>>> get 1.6 out without too much of a delay.
>>>>
>>>> Please see here for the tickets currently associated with version 1.6:
>>>>
>>>>
>>>> https://issues.apache.org/jira/browse/FINERACT-1482?jql=project%20%3D%20%22Apache%20Fineract%22%20AND%20resolution%20is%20EMPTY%20and%20fixVersion%20%3D%201.6.0%20%20ORDER%20by%20status%20DESC%2C%20priority%20DESC%2C%20updated%20DESC
>>>>
>>>> If there are no objections I'd open the 1.6.0 release branch soon (at
>>>> the latest on Monday). If you need any help then please let me know.
>>>>
>>>> Cheers,
>>>>
>>>> Aleks
>>>>
>>>
>>>
>>> --
>>> *Ed Cable*
>>> President/CEO, Mifos Initiative
>>> edcable@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>>>
>>> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>>> <http://facebook.com/mifos> <http://www.twitter.com/mifos>
>>>
>>>
Re: Let's have a new release (1.6.0)...
Posted by Aleksandar Vidakovic <ch...@monkeysintown.com>.
... I'll get the handful that are associated with me out of the way over
the weekend... non of them are critical, more convenience stuff (like
easier releases)... can be all pushed to later... one PR concerning
simplifying DB configuration is almost ready... and another one that is
basically just a reminder will be closed (was too big of a change, I split
it up in smaller PRs that are already merged).
... and as James said: if you need any help then just let me know.
On Thu, Feb 3, 2022 at 8:17 PM James Dailey <ja...@gmail.com> wrote:
> Alexandar - Let me know if I can help with the process, and great to see
> this underway.
> Regular and frequent releases are important.
>
> If helpful, you can also see the Kanban Board for release 1.6 :
> https://issues.apache.org/jira/projects/FINERACT/versions/12349949
>
> I started to go through some of the unassigned issues and think we can
> safely remove them from 1.6 as no one has taken them up.
> They can be moved to a 1.6.1 or such.
>
> Of the 13 in progress, it looks like you have a few assigned to yourself.
> ;).
>
> I think it is probably more important to make sure that the 89 resolved
> issues get into a stable release.
> It might mean requiring more work on some of them, so we should perhaps
> only include those that contribute to stability, scalability, and
> maintainability.
>
>
> https://cwiki.apache.org/confluence/display/FINERACT/How+to+Release+Apache+Fineract
>
>
>
>
> On Thu, Feb 3, 2022 at 10:34 AM Ed Cable <ed...@mifos.org> wrote:
>
>> Thanks Aleks for spearheading this process once again. I will try to ping
>> any contributors that have open pull requests at the moment or forthcoming
>> PRs.
>>
>> Ed
>>
>> On Thu, Feb 3, 2022 at 10:12 AM Aleksandar Vidakovic <
>> cheetah@monkeysintown.com> wrote:
>>
>>> Hi everyone,
>>>
>>> ... it has been a while since our last 1.5.0 release, and since then
>>> we've added and updated quite a bit. Among the usual fixes and improvements
>>> we have major dependency upgrades (Spring, Spring Boot, Jersey) and got rid
>>> of Spring XML configuration while still maintaining 100% backwards
>>> compatibility. I think these changes are worth a new release, so I'm
>>> proposing to have a 1.6.0 release soon (in February) before this gets too
>>> big.
>>>
>>> It would be great if you could all have a look at Jira and either
>>> fix/close the tickets associated with version 1.6 and add anything that
>>> really needs to go into this release. Keep in mind that we'll have other
>>> patch (1.6.1, 1.6.2...) and minor releases (1.7.0....). Would be great if
>>> we can move tickets that are not essential to a later release... just to
>>> get 1.6 out without too much of a delay.
>>>
>>> Please see here for the tickets currently associated with version 1.6:
>>>
>>>
>>> https://issues.apache.org/jira/browse/FINERACT-1482?jql=project%20%3D%20%22Apache%20Fineract%22%20AND%20resolution%20is%20EMPTY%20and%20fixVersion%20%3D%201.6.0%20%20ORDER%20by%20status%20DESC%2C%20priority%20DESC%2C%20updated%20DESC
>>>
>>> If there are no objections I'd open the 1.6.0 release branch soon (at
>>> the latest on Monday). If you need any help then please let me know.
>>>
>>> Cheers,
>>>
>>> Aleks
>>>
>>
>>
>> --
>> *Ed Cable*
>> President/CEO, Mifos Initiative
>> edcable@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>>
>> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>> <http://facebook.com/mifos> <http://www.twitter.com/mifos>
>>
>>
Re: Let's have a new release (1.6.0)...
Posted by James Dailey <ja...@gmail.com>.
Alexandar - Let me know if I can help with the process, and great to see
this underway.
Regular and frequent releases are important.
If helpful, you can also see the Kanban Board for release 1.6 :
https://issues.apache.org/jira/projects/FINERACT/versions/12349949
I started to go through some of the unassigned issues and think we can
safely remove them from 1.6 as no one has taken them up.
They can be moved to a 1.6.1 or such.
Of the 13 in progress, it looks like you have a few assigned to yourself.
;).
I think it is probably more important to make sure that the 89 resolved
issues get into a stable release.
It might mean requiring more work on some of them, so we should perhaps
only include those that contribute to stability, scalability, and
maintainability.
https://cwiki.apache.org/confluence/display/FINERACT/How+to+Release+Apache+Fineract
On Thu, Feb 3, 2022 at 10:34 AM Ed Cable <ed...@mifos.org> wrote:
> Thanks Aleks for spearheading this process once again. I will try to ping
> any contributors that have open pull requests at the moment or forthcoming
> PRs.
>
> Ed
>
> On Thu, Feb 3, 2022 at 10:12 AM Aleksandar Vidakovic <
> cheetah@monkeysintown.com> wrote:
>
>> Hi everyone,
>>
>> ... it has been a while since our last 1.5.0 release, and since then
>> we've added and updated quite a bit. Among the usual fixes and improvements
>> we have major dependency upgrades (Spring, Spring Boot, Jersey) and got rid
>> of Spring XML configuration while still maintaining 100% backwards
>> compatibility. I think these changes are worth a new release, so I'm
>> proposing to have a 1.6.0 release soon (in February) before this gets too
>> big.
>>
>> It would be great if you could all have a look at Jira and either
>> fix/close the tickets associated with version 1.6 and add anything that
>> really needs to go into this release. Keep in mind that we'll have other
>> patch (1.6.1, 1.6.2...) and minor releases (1.7.0....). Would be great if
>> we can move tickets that are not essential to a later release... just to
>> get 1.6 out without too much of a delay.
>>
>> Please see here for the tickets currently associated with version 1.6:
>>
>>
>> https://issues.apache.org/jira/browse/FINERACT-1482?jql=project%20%3D%20%22Apache%20Fineract%22%20AND%20resolution%20is%20EMPTY%20and%20fixVersion%20%3D%201.6.0%20%20ORDER%20by%20status%20DESC%2C%20priority%20DESC%2C%20updated%20DESC
>>
>> If there are no objections I'd open the 1.6.0 release branch soon (at the
>> latest on Monday). If you need any help then please let me know.
>>
>> Cheers,
>>
>> Aleks
>>
>
>
> --
> *Ed Cable*
> President/CEO, Mifos Initiative
> edcable@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>
> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
> <http://facebook.com/mifos> <http://www.twitter.com/mifos>
>
>
Re: Let's have a new release (1.6.0)...
Posted by Ed Cable <ed...@mifos.org>.
Thanks Aleks for spearheading this process once again. I will try to ping
any contributors that have open pull requests at the moment or forthcoming
PRs.
Ed
On Thu, Feb 3, 2022 at 10:12 AM Aleksandar Vidakovic <
cheetah@monkeysintown.com> wrote:
> Hi everyone,
>
> ... it has been a while since our last 1.5.0 release, and since then we've
> added and updated quite a bit. Among the usual fixes and improvements we
> have major dependency upgrades (Spring, Spring Boot, Jersey) and got rid of
> Spring XML configuration while still maintaining 100% backwards
> compatibility. I think these changes are worth a new release, so I'm
> proposing to have a 1.6.0 release soon (in February) before this gets too
> big.
>
> It would be great if you could all have a look at Jira and either
> fix/close the tickets associated with version 1.6 and add anything that
> really needs to go into this release. Keep in mind that we'll have other
> patch (1.6.1, 1.6.2...) and minor releases (1.7.0....). Would be great if
> we can move tickets that are not essential to a later release... just to
> get 1.6 out without too much of a delay.
>
> Please see here for the tickets currently associated with version 1.6:
>
>
> https://issues.apache.org/jira/browse/FINERACT-1482?jql=project%20%3D%20%22Apache%20Fineract%22%20AND%20resolution%20is%20EMPTY%20and%20fixVersion%20%3D%201.6.0%20%20ORDER%20by%20status%20DESC%2C%20priority%20DESC%2C%20updated%20DESC
>
> If there are no objections I'd open the 1.6.0 release branch soon (at the
> latest on Monday). If you need any help then please let me know.
>
> Cheers,
>
> Aleks
>
--
*Ed Cable*
President/CEO, Mifos Initiative
edcable@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
*Collectively Creating a World of 3 Billion Maries | *http://mifos.org
<http://facebook.com/mifos> <http://www.twitter.com/mifos>