+1 (binding) - Followed the release helper guide steps, everything was in good order. - Tested build on both ubuntu 22.04 / GCC 11 and windows 10, with a wide range of extensions. Couldn't build on Arch Linux / GCC 11 because of some weird local toolchain issue that only happens on my desktop. Also failed on Ubuntu/Clang due to MINIFICPP-2005 (fixed on main), but I don't think either of these are blockers. - I saw the failure of PutTCPTests, but that is a known issue of the test (MINIFICPP-2003, fixed on main), and not a bug in PutTCP. - Tested with CWEL -> InvokeHTTP (win) // ListenHTTP -> LogAttribute (linux). It worked fine.
Thanks for RMing! Marton On Wed, 7 Dec 2022 at 11:33, Martin Zink <martinz...@apache.org> wrote: > > +1 (non-binding) > > -Verified signature, hashes and git commit hash > -Built it from source with all extensions on Ubuntu 22.04 > -Verified the new PutTCP and ListenTCP processors with two agents > communicating with each other > > > Thanks, > Martin > > On Mon, Dec 5, 2022 at 3:41 PM Gábor Gyimesi <gamezb...@gmail.com> wrote: > > > +1 (non-binding) > > > > - Verified that binaries are no longer in the source archive > > - Verified signature, hashes and git commit hash > > - Built RC2 core and all extensions (excluding Tensorflow) with GCC 11.3 on > > Ubuntu 22.04 > > - Ran all unit, integration and docker system tests > > - Verified contents of README.md, NOTICE, and LICENSE files > > - Verified built binary with simple flows having TailFile, PutFile, > > GenerateFlowFile, LogAttribute processors and communication through > > InvokeHTTP processor with NiFi's ListenHTTP processor > > - Verified Prometheus metrics reporting with built binary and Prometheus > > 2.35.0 > > > > Thanks, > > Gabor > > > > On Mon, 5 Dec 2022 at 15:00, Ferenc Gerlits <fgerl...@apache.org> wrote: > > > > > On Mon, Dec 5, 2022 at 2:29 PM John McGinn wrote: > > > > > > > Just a note, but the issues closed/resolved list is inaccessible to > > the > > > > public. Not sure if it is meant to be that way or not. > > > > > > > > The release notes link right below it is accessible though. > > > > > > > > Thanks for raising this! It seems to be some weirdness in Jira. We > > may > > > have to use the simpler "tickets closed in this release" page: > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520&version=12351771 > > > in future release emails -- that one seems to be accessible by anonymous > > > users. > > > > > > Thanks, > > > Ferenc > > > > >
