Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/1188
Most of the refactoring for separating the repos is done. The script
changed around a lot, but is largely relocating + making input easier/more
valid. Couple bit and pieces here and there left to do, but it will currently
produce separate repos which artifacts as expected, but not push them.
Made some changes to make life easier.
- It's more like some of the other scripts, in that it prompts you for info
rather than requiring a bunch of flags. Might be worth putting the flags back
in case we want to script this into Maven or something? I thought it made it a
bit clearer what was happening during testing
- More input validation. E.g. version is x.y.z., signing key is reasonably
constructed, etc.
Outstanding questions
- What do we do about the KEYS file? Right now it lives entirely in the
Metron repo, It'd be a rare issue, but things could be weird under the
following circumstances.
1. There's a new release manager without their key in the KEYS file
2. We're releasing the Bro plugin before Metron.
Should this repo have it's own KEYS file? Pull it from the Metron repo?
Ignore/document the problem since it's presumably rare? <Other ideas here>?
Misc
- The pushes are currently commented out. Yes, there's practice run mode,
but I was not going to even slightly depend on that during a refactoring while
a release was going on.
- Nope, this isn't handling non-master branches. Probably pretty easy to
do, just didn't.
---
