You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@fineract.apache.org by "Michael Vorburger (Jira)" <ji...@apache.org> on 2020/08/25 22:47:00 UTC

[jira] [Commented] (FINERACT-876) Automate Fineract release process

    [ https://issues.apache.org/jira/browse/FINERACT-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17184773#comment-17184773 ] 

Michael Vorburger commented on FINERACT-876:
--------------------------------------------

I agree, re. above. FINERACT-1129 is (about to) contribute the most important parts.

> Automate Fineract release process
> ---------------------------------
>
>                 Key: FINERACT-876
>                 URL: https://issues.apache.org/jira/browse/FINERACT-876
>             Project: Apache Fineract
>          Issue Type: Improvement
>            Reporter: Michael Vorburger
>            Priority: Major
>
> While I was making some minor edits to improve our [How to Release Apache Fineract|https://cwiki.apache.org/confluence/x/DRwIB] page on the Wiki for a possible upcoming Fineract 1.4.0 release in FINERACT-873, I was wondering if much of what is listed on that page, like all the git operations, email sending, verification, GPG stuff, even Wiki page creation (Confluence has a REST API...) could not just be fully automated and scripted...



--
This message was sent by Atlassian Jira
(v8.3.4#803005)