Team I believe we're there with 1.16.1
https://issues.apache.org/jira/projects/NIFI/versions/12351504 I'll try to start the RC process today but tomorrow is more likely. Please don't tag anything to 1.16.1 - I'll grab things that land on main if they seem appropriate. Thanks On Thu, Apr 14, 2022 at 10:24 AM Joe Witt <joe.w...@gmail.com> wrote: > Team, > > Looks like the final item we need is here > https://issues.apache.org/jira/browse/NIFI-9883. It is listed as an > improvement but could certainly be viewed through the lens of a bug. > Basically we introduced a library at a level it should not be and we need > to clean that up. > > https://issues.apache.org/jira/projects/NIFI/versions/12351504 > > This will be the most impressive stability release on the heals of a > feature release we've ever done and in record time. Huge thanks to all > contributors. This includes various findings/bug fixes from things that > have popped up in JIRA, on the mailing list, and in Slack as well as things > found/fixed by committers. Really great stuff. > > I expect that the last JIRA will land early next week. Will watch closely > and as soon as it does I intend to initiate RC1 assuming nothing else has > emerged that needs immediate attention. > > Thanks > > On Mon, Apr 11, 2022 at 3:23 PM Joe Witt <joe.w...@gmail.com> wrote: > >> Team, >> >> Am keeping support/nifi-1.16 aligned with fixes that land on main. >> Focusing on >> https://issues.apache.org/jira/projects/NIFI/versions/12351504 to be >> clear on when it is time to kick out 1.16.1. Already more than 50 >> JIRAs/fixes on here! >> >> Thanks >> >> On Tue, Apr 5, 2022 at 6:25 AM David Handermann < >> exceptionfact...@apache.org> wrote: >> >>> Joe, >>> >>> Thanks for wrapping up the 1.16.0 release and preparing 1.16.1, there >>> are a >>> handful of bug fixes and dependency updates that will be helpful to >>> include >>> as a part of 1.16.1. >>> >>> I am in the process of reviewing NIFI-7253 upgrading Jackson, it looks >>> like >>> it should be ready, pending successful automated builds. >>> >>> The Avro upgrade for NIFI-7234 covers more ground in terms of upgrading >>> versions, and appears to involve more changes. We definitely should move >>> in >>> that direction, and I think there have been some previous efforts to >>> upgrade Avro dependencies. I can take an initial look at the PR soon, but >>> it would be helpful for others to give it more attention. >>> >>> There are a couple other dependency upgrades I plan to put forward soon, >>> so >>> perhaps waiting until Wednesday would give a bit more time to get some of >>> those completed. >>> >>> Regards, >>> David Handermann >>> >>> On Mon, Apr 4, 2022 at 3:45 PM Mike Thomsen <mikerthom...@gmail.com> >>> wrote: >>> >>> > I have a few PRs for standardizing and updating our dependencies like >>> > Jackson and Avro. Might be good to get those included in 1.16.1 >>> > >>> > On Mon, Apr 4, 2022 at 3:02 PM Joe Witt <joe.w...@gmail.com> wrote: >>> > > >>> > > Team, >>> > > >>> > > Sorry for the delays in wrapping up the 1.16 release from earlier >>> last >>> > > week. We had great vote turnout and it was definitely a large >>> release in >>> > > terms of features/etc.. >>> > > >>> > > Watching evolution on the 1.17 line since it is clear we can benefit >>> > from a >>> > > 1.16.1 release so I've started preparing that and will closely >>> monitor >>> > > candidates for inclusion. >>> > > >>> > > The branch is pushed and is called 'support/nifi-1.16'. I've already >>> > > pulled in everything on 1.17 that looks like it can work in a pure >>> 3rd >>> > > digit release. Some of this makes sense due to bugs found and or >>> natural >>> > > concerns of scanners for things like springshell/etc.. In any case >>> it is >>> > > always good to tighten up the release lines if time permits. >>> > > >>> > > I'll probably start the release process tomorrow or Wednesday. Will >>> > watch >>> > > for anything that comes in. >>> > > >>> > > Thanks >>> > >>> >>
