[
https://issues.apache.org/jira/browse/METRON-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16607320#comment-16607320
]
ASF GitHub Bot commented on METRON-1769:
----------------------------------------
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/1188
> I'm assuming this always pulls HEAD from master to cut the release. Do we
need or desire any support for cutting a release from a non-HEAD commit?
It would be very useful to continue to merge PRs into master while a
release is being voted on.
I had thought that @mattf-horton use to do the releases in such a way that
this was not a problem, but I could be wrong.
For example, this morning I merged PR #1174 into master that I don't
necessarily want in the next release. I didn't think about the potential
impact to the release if we have to cut a new RC. Sorry about that @justinleet
.
> 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)
