I did a bit of poking around and I don't believe we ever formally wrote
that down.  The last release happened as a combination of actions from
mattf and myself (mostly mattf).

The plugin has two new commits since the last release (1 bugfix 1 feature)
- if we want to couple version 0.2 of the plugin with a metron 0.5.0 release we
would need to make a 0.2 tag against HEAD of the plugin repo, then
increment the version in the ansible playbooks here

Or, if we just want to make a plugin release without changing
apache/metron, we could just make a 0.2 tag in the plugin repo, and then
release it in a more disjointed way.  I know that's not super helpful since
I don't have documentation for doing an apache release of the plugin other
than hacking something together based on what's out there for apache/metron.

Reference conversations:


On Fri, May 25, 2018 at 2:00 PM Justin Leet <justinjl...@gmail.com> wrote:

> At the risk of exposing my ignorance, do we have the bro plugin release
> process documented anywhere?  We have a doc for the main release (
> https://cwiki.apache.org/confluence/display/METRON/Release+Process), but I
> haven't noticed one for the bro plugin.
> For the current RC, it's not included and it wasn't pushed for (it has less
> changes for obvious reasons).  However, we should be making sure to
> validate if its necessary to release and having the process documented.
> Justin


Reply via email to