Re: Bro plugin release process docs?

I've updated the cwiki and opened a PR for this, open to feedback on any of the changes I made/suggested. Since I assume we wouldn't want to make any changes to

Re: Bro plugin release process docs?

Okay, I'll PR something since I'm looking at it Jon On Thu, Oct 11, 2018 at 9:45 AM Justin Leet wrote: > If I recall correctly, they were already different, presumably from the > more manual process, and I wanted keep things close to what they already > were before trying to clean that sort of

Re: Bro plugin release process docs?

Is there a reason why the prefix for apache/metron ends with a -, whereas the plugin ends with a _ separator? I would like to see it more uniform using the _ Jon On Thu, Oct 11, 2018 at 9:04 AM Justin Leet wrote: > That first half of that page will be rewritten in the next couple days to >

Re: Bro plugin release process docs?

That first half of that page will be rewritten in the next couple days to reflect the script to prepare release candidate; I didn't want to change that page until the PR actually went in. The release process, barring the KEYS issue (and a patch to the script to handle the bro plugin tag), is

Re: Bro plugin release process docs?

Yeah you're right when I looked closer to make the change it was step 10. I pushed a manual 0.2 tag to metron-bro-plugin-kafka and did a quick update to the cwiki, but it could use some additional love, especially if we want to split out the release processes generally. Jon On Wed, Oct 10, 2018

Re: Bro plugin release process docs?

Yeah, we need to update the release process instructions. It should actually be step 10 shouldn't it? We want to keep the rc tag as-is because it may get rejected/cancelled, and update the final tag as the release. I already need to overhaul that page to reflect the addition of the RC creation

Re: Bro plugin release process docs?

+1 to all of that from me, Jon. Thanks for taking care of this. On Wed, Oct 10, 2018 at 2:34 PM zeo...@gmail.com wrote: > I wonder if we should also update the > https://cwiki.apache.org/confluence/display/METRON/Release+Process > instructions > to include tagging for the bro plugin, or if we

Re: Bro plugin release process docs?

I wonder if we should also update the https://cwiki.apache.org/confluence/display/METRON/Release+Process instructions to include tagging for the bro plugin, or if we were going to split out the release processes? I'd be happy to update the instructions (Step 8) if that's the right place for now

Re: Bro plugin release process docs?

So I was poking around on the plugin today and noticed that we have a apache-metron-bro-plugin-kafka_0.2.0-release and apache-metron-bro-plugin-kafka_0.2.0-rc1 tag, but no 0.2 (which is what bro-pkg would point to). Anybody have any concerns if I push the 0.2 tag as discussed above? Then we

Re: Bro plugin release process docs?

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

Bro plugin release process docs?

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