You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "yifan zou (Jira)" <ji...@apache.org> on 2019/09/03 21:46:00 UTC

[jira] [Resolved] (BEAM-8117) Improve the preparation_before_release script

     [ https://issues.apache.org/jira/browse/BEAM-8117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

yifan zou resolved BEAM-8117.
-----------------------------
    Fix Version/s: Not applicable
       Resolution: Fixed

> Improve the preparation_before_release script
> ---------------------------------------------
>
>                 Key: BEAM-8117
>                 URL: https://issues.apache.org/jira/browse/BEAM-8117
>             Project: Beam
>          Issue Type: Sub-task
>          Components: project-management
>            Reporter: yifan zou
>            Assignee: yifan zou
>            Priority: Major
>             Fix For: Not applicable
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> * Setup GPG keys: 
>  * The preparation_before_release.sh interrupted. Git command failed when configuring git signing key.
>  * It required a PMC to add the key in dev@ list, the script doesn’t really help.
>  * Apache requires the key has at least 4096 bits, but script generates the 3072b key by default. There were a few options to select the size of the key, but there was no instruction indicates which option the release manager should choose. 
>  * *Solution*: I follow the Apache official [release signing guide|https://www.apache.org/dev/release-signing.html] to generate the RSA keys then asked a PMC member adding it to the dev and release key list.
>  * Reference: [GPG Cheat Sheet|http://irtfweb.ifa.hawaii.edu/~lockhart/gpg/]



--
This message was sent by Atlassian Jira
(v8.3.2#803003)