Hi community, I'd like to initiate a discussion about the next release of MiNiFi C++. The last release was more than four months ago, and there have been many new features, bug fixes and stability improvements committed to the development branch since then: 71 tickets closed, over 96 commits as of today.
I would be happy to take on RM duties for this release. Notable features and improvements since the 0.14.0 release: - ConsumeWindowsEventLog can work from log files - ConsumeWindowsEventLog resolve Security/UserID attribute - TLS v1.3 support - PutS3Object multipart upload support - Use systemd service management on Linux - Add ProcessContext::getStateManager to Lua/Python - Reworked GetTCP to be more inline with ListenTCP - SSL support for Prometheus reporter - Documentation improvements - Multiarch docker support - RFC3339 parsing with expression language - Reworked Minifi controller - gcc-13 support - Fix for waking up prematurely after processor yields - Fix system certificate store usage in SSLContextService on Linux - Fix inconsistent naming in C2 machineArch - Fix default CA path for S3 on CentOS - Removed CronScheduler locale requirements We've upgraded our third party dependencies (notable mentions) - Replaced LibreSSL with OpenSSL 3.1.1 - Upgraded RocksDB to v8.1.1 - Upgraded LibCurl to v8.1.0 - Upgraded CivetWeb to v1.16 - Upgraded OpenCV to v4.7.0 - Upgraded GoogleCloud SDK to v2.10.1 - Upgraded Azure SDK to v12.7.0 The core API is still not mature enough to be able to commit to it, so in line with previous discussions I suggest releasing it as 0.15.0. Do you agree it is time for a new release? Are there any blockers that we should definitely include in this release? Thanks, Martin
