Hi everyone,

... just wanted to chime in quickly and give you an update on my setup
status; I'm using my Apache email address "[email protected]"; on Jira and
Confluence the username is "aleks"

   - created my Apache GPG key; I guess it needs to be added to
   https://downloads.apache.org/fineract/KEYS
   - I had a first read of the release process
   
https://cwiki.apache.org/confluence/display/FINERACT/How+to+Release+Apache+Fineract
   
<https://www.google.com/url?q=https://cwiki.apache.org/confluence/display/FINERACT/How%2Bto%2BRelease%2BApache%2BFineract&sa=D&source=hangouts&ust=1596542482991000&usg=AFQjCNGX48IGBCFcIWO_zWU3wGwt-dyWng>
   (has anything changed? please let me know)
   - it seems that I have enough permissions on Fineract Jira (can't hurt
   to check that again)
   - I think some permissions Fineract's Confluence space are missing
   (can't edit pages)
   - permissions to be able to create releases on Github repository are
   missing
   - anything else I missed?

@Michael Vorburger <[email protected]> could you help me out to
get these last steps done? Maybe we can have a short meeting to sort this
out?

When this is done I'd like to get things started and announce the 2 weeks
code freeze before the release date.

Looking forward to helping out.

Cheers,

Aleks

On Mon, Aug 3, 2020 at 1:48 AM Michael Vorburger <[email protected]> wrote:

> Hello,
>
> On Thu, 30 Jul 2020, 01:58 Ed Cable, <[email protected]> wrote:
>
>> Michael,
>>
>> Aleks has graciously volunteered to take on the role of release manager
>> for the Fineract 1.4 release. I'm really happy he's stepping forward to
>> take this duty on as he's active within our implementer community having
>> done development work for Fiter. His example will hopefully motivate other
>> ecosystem players to help take on some of these core duties.
>>
>
> Great to hear.
>
> He's famliarizing himself with the steps of the process you so thoroughly
>> documented at
>> https://cwiki.apache.org/confluence/display/FINERACT/How+to+Release+Apache+Fineract
>>  and
>> making sure he has the tools and permissions). The one step (since he's
>> only a committer and not part of PMC) he will need assistance with is
>> uploading the release ZIP
>>
>
> I'm happy to try to help with that, once we get to that step. (Without
> being to commit to being able to immediately reply.)
>
> Given that we've been waiting so long to do the 1.4 release, I wasn't sure
>> where we were in the process (i.e. did Aleks still have to formally
>> announce the release branch and start the 2 week time clock for the branch
>> point).
>>
>
> Yes. Fineract hasn't had a 1.4.0 release yet, because there never was the
> required heads up public list emails, discussions, waiting period, and PMC
> vote.
>
> BTW the existing old 1.4 tag in Git must be deleted.
>
> Back in May, we had published 1.4 release notes at
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12344606&styleName=Html&projectId=12319420&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED_5c1a48ffe387dac1f01cd0650aea24d683fe3588_lin
>>
>
> We'll need to do some JIRA clean up, as this list includes a number of
> issues tagged with Fix Version 1.4.0 which are still open. Some of them may
> still make it, others will need to have their Fix Version changed.
>
> which has continued to grow with all the pull requests that have since
>> merged.
>>
>> I'll let you clarify on that point in this email and then I'll have Aleks
>> carry forward with the release process.
>>
>
> Looking forward.
>
> Cheers,
>>
>> Ed
>>
>

Reply via email to