Update on the progress of this release: I wanted to post the RC this
week, but new issues kept creeping up while preparing, so I don't think
I'll be able to do that. I've added notes about the fixes the team did
this week in the release Jira ticket:
https://issues.apache.org/jira/browse/MINIFICPP-2510
I'm hoping to prepare the RC next Monday/Tuesday, if no important new
issues pop up.
(I know about the typo in the subject line. I've proofread the contents,
but not the subject before sending. Oopsies. 😅)
Marton
On 1/15/25 2:25 PM, Joe Witt wrote:
Looks like a good plan
On Wed, Jan 15, 2025 at 5:03 AM Gábor Gyimesi <lordga...@apache.org> wrote:
+1 and thank you for RMing!
I agree, even if 1.0 is still not ready, there have been a lot of new
added features and improvements so it's high time for a new release.
I hope 1.0 can follow shortly after this release and have a more
frequent release schedule after that.
Regards,
Gabor
On Tue, 14 Jan 2025 at 14:21, Marton Szasz <sza...@apache.org> wrote:
Hi NiFi team,
I propose a second pre-1.0 release of MiNiFi C++. There is still a large
refactoring effort underway, but there were plenty of fixes and
improvements committed since the last release, which was in last May.
A few examples:
- Countless fixes and improvements to NiFi 2.0-compatible Python
processor support
- added support for parameter substitution
- added support for recordsets
- added new components: Couchbase, SplitContent, SegmentContent,
SplitRecord, FetchModbusTcp
- changed defaults for logging and RocksDB repositories
- dropped poorly maintained bits, such as JNI, USB camera, sensors, Pcap
and OpenWSMAN extensions, and nanofi
- improved performance of event driven scheduling
- fixed various thread safety and type safety bugs (note: I'm not aware
of any vulnerabilities caused by them)
- ListenHTTP now only reads from the network while scheduled, and
respects connection queue limits
I'm happy to take on RM duties.
Thanks,
Marton
