Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/1188
@nickwallen Updated the script.
I did a few things in the latest commits.
* reorganized slightly the order of prompts
* Fixed the last (non-KEYS file) TODO
* Uncommented out the pushes.
* Allow for arbitrary hash or branch name for the base of the RC.
* Fixed how the metron-bro-kafka-plugin handles the tag (turns out I tagged
it as 0.2.0-release instead of 0.2-release, so I'm just going forward with
that).
To summarize, at this point the script
* Can be run independently for either the top level module or the bro
submodule.
* The script prompts you for the appropriate inputs to set this up.
* Practice run mode allows for the script to be dry-run and outputs the
commands it would have run.
* The script will let you create an RC from a given revision (or branch),
but will not let you cherry-pick commits.
Outstanding issues
* Adjust the -rcN. Actually not sure what to do about this. I think we'd
have to set the base folder name of the tar appropriately at creation time, but
the catch is that we sign everything so it's set in stone when we do. We could
just not have it on the base folder of the RC tar file and keep the tar file
named with -rcN. I don't know if it actually matters
* The whole KEYS file thing. From what I can tell this only needs to exist
at the root of dist. It might be worthwhile to just keep it in the metron
project, and have the instructions for merging that PR tell how to do it
separately (e.g. somewhat similar to the site being more standalone). I'm
going to reply to the thread about original split to see if anybody has an
opinion
---
