Re: Fineract 1.5.0 release branch

[Bharath Gowda]

+1 for the release
Regards,
Bharath
Lead Implementation Analyst | Mifos Initiative
Skype: live:cbharath4| Mobile: +91.7019635592
http://mifos.org  



On Fri, May 21, 2021 at 6:57 PM Aleksandar Vidakovic <
chee...@monkeysintown.com> wrote:

> +1
>
> On Fri, May 21, 2021 at 3:19 PM Petri Tuomola 
> wrote:
>
>> All
>>
>>
>> As previously announced, I've just created the release branch for our 
>> upcoming 1.5.0 release.
>>
>> You can continue working and merging PRs to the develop branch for future 
>> releases, as always.
>>
>> The DRAFT release notes are on 
>> https://cwiki.apache.org/confluence/display/FINERACT/1.5.0+-+Apache+Fineract.
>>   Does anyone see anything missing?
>>
>> Does anyone have any last minutes changes they would like to see 
>> cherry-picked to branch 1.5.0, or are we good go and actually cut the 
>> release based on this branch as it is?
>>
>> I'll initiate the final stage of actually creating the release on Sunday 
>> 23rd May if nobody objects.
>>
>> Thanks,
>> Petri
>>
>>
>>

Re: Fineract 1.5.0 release branch

[Aleksandar Vidakovic]

+1

On Fri, May 21, 2021 at 3:19 PM Petri Tuomola 
wrote:

> All
>
>
> As previously announced, I've just created the release branch for our 
> upcoming 1.5.0 release.
>
> You can continue working and merging PRs to the develop branch for future 
> releases, as always.
>
> The DRAFT release notes are on 
> https://cwiki.apache.org/confluence/display/FINERACT/1.5.0+-+Apache+Fineract. 
>  Does anyone see anything missing?
>
> Does anyone have any last minutes changes they would like to see 
> cherry-picked to branch 1.5.0, or are we good go and actually cut the release 
> based on this branch as it is?
>
> I'll initiate the final stage of actually creating the release on Sunday 23rd 
> May if nobody objects.
>
> Thanks,
> Petri
>
>
>

Re: Fineract 1.5.0 release branch

[Petri Tuomola]

All

As previously announced, I've just created the release branch for our upcoming 
1.5.0 release.  

You can continue working and merging PRs to the develop branch for future 
releases, as always.

The DRAFT release notes are on 
https://cwiki.apache.org/confluence/display/FINERACT/1.5.0+-+Apache+Fineract.  
Does anyone see anything missing?

Does anyone have any last minutes changes they would like to see cherry-picked 
to branch 1.5.0, or are we good go and actually cut the release based on this 
branch as it is?

I'll initiate the final stage of actually creating the release on Sunday 23rd 
May if nobody objects.

Thanks,
Petri

Re: Fineract 1.5.0 release branch

[Aleksandar Vidakovic]

... @Petri Tuomola  ... and if you get stuck
somewhere then just let me know.

On Fri, May 21, 2021 at 3:51 AM Ed Cable  wrote:

> Petri,
>
> Thanks for stepping up to help Aleks and the rest of the Fineract
> community. Given the imperative in getting this release out, it would be
> great if you can continue to proceed ahead with the steps for releasing as
> you've been following at
>
>
> https://cwiki.apache.org/confluence/display/FINERACT/How+to+Release+Apache+Fineract
>
> I think next up will be Step 5 from that list in freezing JIRA, creating
> release tag, building distribution, digitally signing it, uploading it to
> dist/dev (staging), and calling for the PMC vote which we'll need to have
> open for at least 72 hours or at least 3 +1s from the PMC.
>
> Ed
>
> On Thu, May 20, 2021 at 4:36 PM Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> Hi Petri,
>>
>> ... thanks for stepping in... I got a bit side-tracked, because my main
>> dev machine went up in flames and unfortunately I forgot to make a backup
>> of my GPG keys. At least I have a new machine; the last thing I need to do
>> is retrieve my keys from an nvme ssd (can't believe how difficult it is to
>> get an external casing for that). I should be back on track by Monday...
>> I'll sync with you to see how I can help out again.
>>
>> Cheers,
>>
>> Aleks
>>
>>
>> On Fri, May 21, 2021 at 12:39 AM Petri Tuomola 
>> wrote:
>>
>>> Hello all - hope you are staying safe and healthy
>>>
>>> For a number of reasons, I think it is important that we get the next
>>> release - Fineract 1.5.0 - out as soon as possible. I know Aleks was
>>> working on this - not sure how far you got with this Aleks?
>>>
>>> However, I’d be happy to help get this over the line. So unless someone
>>> else wants to do this, or has any objections, I will create a 1.5.0 branch
>>> off develop in our git repository at https://github.com/apache/fineract
>>> on Saturday 22nd May. I will also then create a release tracking umbrella
>>> issue for tracking all activity in JIRA.
>>>
>>> If you’d prefer another approach, or if you’d like to take care of this
>>> (or have already started working not this), please drop me a note before
>>> tomorrow so we don’t duplicate any work.
>>>
>>> Thanks everyone
>>>
>>> Regards
>>> Petri
>>>
>>>
>>>
>
> --
> *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 1.5.0 release branch

[Ed Cable]

Petri,

Thanks for stepping up to help Aleks and the rest of the Fineract
community. Given the imperative in getting this release out, it would be
great if you can continue to proceed ahead with the steps for releasing as
you've been following at

https://cwiki.apache.org/confluence/display/FINERACT/How+to+Release+Apache+Fineract

I think next up will be Step 5 from that list in freezing JIRA, creating
release tag, building distribution, digitally signing it, uploading it to
dist/dev (staging), and calling for the PMC vote which we'll need to have
open for at least 72 hours or at least 3 +1s from the PMC.

Ed

On Thu, May 20, 2021 at 4:36 PM Aleksandar Vidakovic <
chee...@monkeysintown.com> wrote:

> Hi Petri,
>
> ... thanks for stepping in... I got a bit side-tracked, because my main
> dev machine went up in flames and unfortunately I forgot to make a backup
> of my GPG keys. At least I have a new machine; the last thing I need to do
> is retrieve my keys from an nvme ssd (can't believe how difficult it is to
> get an external casing for that). I should be back on track by Monday...
> I'll sync with you to see how I can help out again.
>
> Cheers,
>
> Aleks
>
>
> On Fri, May 21, 2021 at 12:39 AM Petri Tuomola 
> wrote:
>
>> Hello all - hope you are staying safe and healthy
>>
>> For a number of reasons, I think it is important that we get the next
>> release - Fineract 1.5.0 - out as soon as possible. I know Aleks was
>> working on this - not sure how far you got with this Aleks?
>>
>> However, I’d be happy to help get this over the line. So unless someone
>> else wants to do this, or has any objections, I will create a 1.5.0 branch
>> off develop in our git repository at https://github.com/apache/fineract
>> on Saturday 22nd May. I will also then create a release tracking umbrella
>> issue for tracking all activity in JIRA.
>>
>> If you’d prefer another approach, or if you’d like to take care of this
>> (or have already started working not this), please drop me a note before
>> tomorrow so we don’t duplicate any work.
>>
>> Thanks everyone
>>
>> Regards
>> Petri
>>
>>
>>

-- 
*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 1.5.0 release branch

[Aleksandar Vidakovic]

Hi Petri,

... thanks for stepping in... I got a bit side-tracked, because my main dev
machine went up in flames and unfortunately I forgot to make a backup of my
GPG keys. At least I have a new machine; the last thing I need to do is
retrieve my keys from an nvme ssd (can't believe how difficult it is to get
an external casing for that). I should be back on track by Monday... I'll
sync with you to see how I can help out again.

Cheers,

Aleks


On Fri, May 21, 2021 at 12:39 AM Petri Tuomola 
wrote:

> Hello all - hope you are staying safe and healthy
>
> For a number of reasons, I think it is important that we get the next
> release - Fineract 1.5.0 - out as soon as possible. I know Aleks was
> working on this - not sure how far you got with this Aleks?
>
> However, I’d be happy to help get this over the line. So unless someone
> else wants to do this, or has any objections, I will create a 1.5.0 branch
> off develop in our git repository at https://github.com/apache/fineract
> on Saturday 22nd May. I will also then create a release tracking umbrella
> issue for tracking all activity in JIRA.
>
> If you’d prefer another approach, or if you’d like to take care of this
> (or have already started working not this), please drop me a note before
> tomorrow so we don’t duplicate any work.
>
> Thanks everyone
>
> Regards
> Petri
>
>
>

Re: Fineract 1.5.0 release branch

[Aleksandar Vidakovic]

Hi everyone,

... first: sorry for the delay, had a couple of distractions I had to
attend to...

Now back to the release... Today I will go over the current set of Jira
issues to see what the situation is... everyone who's currently working on
an issue and thinks that it can get done let's say in the next 2 weeks
should assign it to version 1.5.0 in Jira; please do the same with issues
that should be included in 1.5.0 (independent if someone is working on it).

Would be great if we could get this done in the next couple of days. Once
I'm done sorting things out on Jira I'll publish a list here to give
everyone an overview.

Thanks again for helping out... if you have any questions or need help then
let me know (and let's discuss here on the list).

Cheers,

Aleks

On Tue, Feb 23, 2021 at 8:39 AM James Dailey  wrote:

> I want to thank the contributors.
>
>  We still need to get a release out.
>
> Alexander - can we keep on moving forward?
>
> Michael - can we remove 1.5 as 'fix Branch' designated from all items not
> currently fixed?
>
> Who can also help?
>
>
>
>
>
>
>
>
>
> On Sun, Feb 7, 2021, 6:40 AM Michael Vorburger  wrote:
>
>> Hello everyone,
>>
>> We currently have 111 open issues with Fix Version 1.5.0, see
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20%22Apache%20Fineract%22%20AND%20resolution%20is%20EMPTY%20and%20fixVersion%20%3D%201.5.0%20%20ORDER%20by%20status%20DESC%2C%20priority%20DESC%2C%20updated%20DESC
>>
>> Could we invite any active contributors who have open issues with Fix
>> Version 1.5.0 assigned to yourself EITHER link them to
>> https://issues.apache.org/jira/browse/FINERACT-1305 if you are actively
>> working on them and about to raise a PR, OR remove the 1.5.0 fix version if
>> it's not going to make it for this next release? (I've just done this for
>> all issues that were assigned to me.)
>>
>> Note that the way that this process (has to) work is that only active
>> contributors set Fix Versions; so this is about "I can commit to fixing
>> XYZ" and NOT about "I would like XYZ to be fixed for XYZ - but cannot fix
>> it myself (or pay someone to fix it for me)"... otherwise we would probably
>> never ship.
>>
>> The Release Manager (RM, Aleks) will just remove the Fix Version 1.4.0
>> for anything that doesn't make it, as per
>> https://cwiki.apache.org/confluence/display/FINERACT/How+to+Release+Apache+Fineract
>> .
>>
>> Best,
>> M.
>> ___
>> Michael Vorburger
>> http://www.vorburger.ch
>>
>> On Tue, Jan 26, 2021 at 2:09 PM Aleksandar Vidakovic <
>> chee...@monkeysintown.com> wrote:
>>
>>> Hi everyone,
>>>
>>> Based on our "How to Release Apache Fineract" process documented at
>>> https://cwiki.apache.org/confluence/x/DRwIB :
>>>
>>> I will create a 1.5.0 branch off develop in our git repository at
>>> https://github.com/apache/fineract on Wednesday, February 10, 2020.
>>>
>>> The release tracking umbrella issue for tracking all activity in JIRA
>>> is https://issues.apache.org/jira/browse/FINERACT-1305 for this Fineract
>>> 1.5.0.
>>>
>>> If you have any work in progress that you 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,
>>>
>>> Aleks
>>>
>>

Re: Fineract 1.5.0 release branch

[James Dailey]

I want to thank the contributors.

 We still need to get a release out.

Alexander - can we keep on moving forward?

Michael - can we remove 1.5 as 'fix Branch' designated from all items not
currently fixed?

Who can also help?









On Sun, Feb 7, 2021, 6:40 AM Michael Vorburger  wrote:

> Hello everyone,
>
> We currently have 111 open issues with Fix Version 1.5.0, see
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20%22Apache%20Fineract%22%20AND%20resolution%20is%20EMPTY%20and%20fixVersion%20%3D%201.5.0%20%20ORDER%20by%20status%20DESC%2C%20priority%20DESC%2C%20updated%20DESC
>
> Could we invite any active contributors who have open issues with Fix
> Version 1.5.0 assigned to yourself EITHER link them to
> https://issues.apache.org/jira/browse/FINERACT-1305 if you are actively
> working on them and about to raise a PR, OR remove the 1.5.0 fix version if
> it's not going to make it for this next release? (I've just done this for
> all issues that were assigned to me.)
>
> Note that the way that this process (has to) work is that only active
> contributors set Fix Versions; so this is about "I can commit to fixing
> XYZ" and NOT about "I would like XYZ to be fixed for XYZ - but cannot fix
> it myself (or pay someone to fix it for me)"... otherwise we would probably
> never ship.
>
> The Release Manager (RM, Aleks) will just remove the Fix Version 1.4.0 for
> anything that doesn't make it, as per
> https://cwiki.apache.org/confluence/display/FINERACT/How+to+Release+Apache+Fineract
> .
>
> Best,
> M.
> ___
> Michael Vorburger
> http://www.vorburger.ch
>
> On Tue, Jan 26, 2021 at 2:09 PM Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> Hi everyone,
>>
>> Based on our "How to Release Apache Fineract" process documented at
>> https://cwiki.apache.org/confluence/x/DRwIB :
>>
>> I will create a 1.5.0 branch off develop in our git repository at
>> https://github.com/apache/fineract on Wednesday, February 10, 2020.
>>
>> The release tracking umbrella issue for tracking all activity in JIRA is
>> https://issues.apache.org/jira/browse/FINERACT-1305 for this Fineract
>> 1.5.0.
>>
>> If you have any work in progress that you 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,
>>
>> Aleks
>>
>

Re: Fineract 1.5.0 release branch

[Michael Vorburger]

Hello everyone,

We currently have 111 open issues with Fix Version 1.5.0, see
https://issues.apache.org/jira/issues/?jql=project%20%3D%20%22Apache%20Fineract%22%20AND%20resolution%20is%20EMPTY%20and%20fixVersion%20%3D%201.5.0%20%20ORDER%20by%20status%20DESC%2C%20priority%20DESC%2C%20updated%20DESC

Could we invite any active contributors who have open issues with Fix
Version 1.5.0 assigned to yourself EITHER link them to
https://issues.apache.org/jira/browse/FINERACT-1305 if you are actively
working on them and about to raise a PR, OR remove the 1.5.0 fix version if
it's not going to make it for this next release? (I've just done this for
all issues that were assigned to me.)

Note that the way that this process (has to) work is that only active
contributors set Fix Versions; so this is about "I can commit to fixing
XYZ" and NOT about "I would like XYZ to be fixed for XYZ - but cannot fix
it myself (or pay someone to fix it for me)"... otherwise we would probably
never ship.

The Release Manager (RM, Aleks) will just remove the Fix Version 1.4.0 for
anything that doesn't make it, as per
https://cwiki.apache.org/confluence/display/FINERACT/How+to+Release+Apache+Fineract
.

Best,
M.
___
Michael Vorburger
http://www.vorburger.ch

On Tue, Jan 26, 2021 at 2:09 PM Aleksandar Vidakovic <
chee...@monkeysintown.com> wrote:

> Hi everyone,
>
> Based on our "How to Release Apache Fineract" process documented at
> https://cwiki.apache.org/confluence/x/DRwIB :
>
> I will create a 1.5.0 branch off develop in our git repository at
> https://github.com/apache/fineract on Wednesday, February 10, 2020.
>
> The release tracking umbrella issue for tracking all activity in JIRA is
> https://issues.apache.org/jira/browse/FINERACT-1305 for this Fineract
> 1.5.0.
>
> If you have any work in progress that you 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,
>
> Aleks
>