I would suggest that we institute a release procedure for the package itself, but I don't think it necessarily has to line up with metron releases (happy to be persuaded otherwise). Then we can just link metron to metron-bro-plugin-kafka by pointing to specific metron-bro-plugin-kafka releases (git tags <http://bro-package-manager.readthedocs.io/en/stable/package.html#package-versioning> ).
Right now, full-dev spins up against the apache/metron-bro-plugin-kafka master branch, which is not a good idea to have in place for an upcoming release. That is the crux of why I think we need to finalize the move to bro 2.5.2 and the plugin packaging before our next release (working on it as we speak). Jon On Thu, Nov 16, 2017 at 9:10 AM Nick Allen <n...@nickallen.org> wrote: > The code of the 'Kafka Plugin for Bro' is now maintained in the external > repository that we set up a while back. Do we need to change anything in > the release procedure to account for this? > -- Jon
