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 <[email protected]> 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 <[email protected]> > 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 <[email protected]> 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 > > >
