[
https://issues.apache.org/jira/browse/METRON-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16644943#comment-16644943
]
ASF GitHub Bot commented on METRON-1769:
----------------------------------------
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/1188
@nickwallen @mmiklavc @ottobackwards While I'm loath to look gift +1's in
the mouth, the KEYS file issue still isn't resolved. Is everyone okay with me
making a follow-on ticket to address it and alter the script as necessary?
Possibly add a note in the docs that the jira needs to be resolved (or manually
handled) in the release manager switches case?
> Script creation of a release candidate
> --------------------------------------
>
> Key: METRON-1769
> URL: https://issues.apache.org/jira/browse/METRON-1769
> Project: Metron
> Issue Type: Improvement
> Reporter: Justin Leet
> Assignee: Justin Leet
> Priority: Major
>
> Our process at:
> https://cwiki.apache.org/confluence/display/METRON/Release+Process is fairly
> error prone. There's a lot of typing out versions and other tedious busywork.
> In particular, this JIRA is for steps 4/5, as they're the most egregious.
> This script should be able to produce both the core artifacts as well as the
> bro kafka plugin artifacts.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
