[
https://issues.apache.org/jira/browse/METRON-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16634441#comment-16634441
]
ASF GitHub Bot commented on METRON-1769:
----------------------------------------
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/1188
@nickwallen Same as my last comment. It's been pretty refactored since the
release (in order to handle the discussion we had around releases going
forward). I just haven't had time to sit down and finish polishing it, and
since the release went out it fell in personal priority.
I need to
* Fix one TODO in the code
* Uncomment the pushes, since I didn't want to risk that.
Future fixes
* Handle releases not on master (e.g. from a given commit or from a a given
branch/commit). We could potentially allow for cherry-picking, but I think the
basic cases are sufficient.
* Adjust the -rcN. It's probably easy enough to do in here, but I also
don't consider it necessary.
Outstanding questions
* KEYS file for bro plugin repo, as noted above.
Feel free to rearrange those if you feel differently, I don't really care
if it is follow on, or we do it now.
There's probably some more work to handle any hotfix releases, but we've
never done one, so I'm not super concerned for right now.
> 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)
