A new release is a good idea and I agree with releasing it as 0.11.0. Thanks for RMing it!
Thanks, Martin On Thu, Nov 18, 2021 at 3:27 PM Ferenc Gerlits <[email protected]> wrote: > Yes, it's definitely time for a new release, and 0.11.0 sounds good. > Thanks for RMing! > > Ferenc > > > On Wed, Nov 17, 2021 at 12:09 PM Marton Szasz <[email protected]> wrote: > > > I agree that it's time for a new release, thank you for taking the RM > > duties. I'm not aware of any blockers at the moment. > > > > Thanks, > > Marton > > > > On Wed, 17 Nov 2021 at 10:28, Adam Debreceni <[email protected]> > > wrote: > > > > > > Hi community, > > > > > > I'd like to initiate a discussion about the next release of MiNiFi C++. > > The > > > last release was five months ago, and there have been many new > features, > > > bug fixes and stability improvements committed to the development > branch > > > since. > > > I would be happy to take on RM duties for this release. > > > > > > New features since the 0.10.0 release: > > > - new processors: > > > * AttributesToJson > > > * DefragmentText > > > * PutAzureDataLakeStorage > > > * ReplaceText > > > * RouteText > > > - support for funnels > > > - shared rocksdb repository > > > - repository encryption (flow-file, content) > > > - support for Azure managed identity > > > - modularization of extensions > > > - ConsumeKafka security protocol > > > - platform independent AppendHostInfo > > > - agent configuration checksum in the c2 heartbeat > > > > > > We now use C++17 throughout the codebase and C++20 wherever possible. > > > > > > 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.11.0. > > > > > > Do you agree it is time for a new release? Are there any blockers that > > we > > > should definitely include in this release? > > > > > > Thanks, > > > Adam > > >
