New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zeek renaming: decide if BroControl needs changes #240

jsiwek opened this Issue Jan 11, 2019 · 0 comments


None yet
1 participant
Copy link

jsiwek commented Jan 11, 2019

If BroControl is intended to be replaced by a new supervisor project, it's maybe not worth renaming the project? Or just rename it to avoid confusion?

It's probably likely there will at least be code changes needed to get it to work with all the other renaming going on. E.g. I imagine #239 will probably break BroControl and we can't just release a 2.7 where BroControl is completely broken, we need at least one release of it being in a working, but deprecated state.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment