metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Miklavcic <>
Subject [DISCUSS] Metron Release - 0.7.1 next steps
Date Wed, 01 May 2019 00:47:48 GMT
The vote for RC1 did not pass and I'd like to kickstart some discussion
about what we should do.

I started taking a look at PR#1360 and it looks like this isn't quite as
close to being able go in as I had originally expected. I want to talk
about options here. It seems to me that we can:

   1. Wait for PR#1360 to go in, but this is likely going to take more time
   than originally anticipated
   2. Accept the issue in full dev, but add some notes in the developer
   docs about the current feature gap and why sensors aren't showing status in
   the management UI when aggregation is enabled.
   3. Find some other workable UI solution.
   4. Other option?

All things considered, I'm personally leaning towards #2 in the short-term,
but I think we should probably talk about this a bit before deciding what
RC2 should be.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message