Version 3.0 ideas

[aaronkaplan]

merge into master pls

[ghost]

There are two open pull requests to the branch:

• REST API ideas for 3.0 #1528
• Version 3.0 ideas #1540

Please resolve them first.

There is also a merge conflict in docs/IntelMQ-3.0-Architecture.md.

Merging into master would mean we do a new feature release (2.3.0) with the current state of the develop branch which contains a development version. Additionally, to keep IntelMQ version numbers in sync with IntelMQ Manager's, we'd need to do a IntelMQ Manger 2.3.0 release but the latter is not yet ready, but we are working on it to make it release-ready. I therefore propose, to not merge into master for now. Alternatively we can do a minimal bugfix release by cherry-picking all the commits to the maintenance branch and make a bugfix release, but I don't think it's worth the effort.

[aaronkaplan]

How is the situation now? I think it should be rather easy to "backport"/cherry pick this markdown document so that it's actually visible in develop/master. After all, it's just a document and no code.

[ghost]

There is still an open PR to this branch: #1528

And could please squash the commits?

[kamil-certat]

@aaronkaplan Could you review if this PR is still valid? It looks like something interesting, but I don't know what is still up-to-date