Hello All, I plan to kick off the RC as soon as https://issues.apache.org/jira/browse/NIFI-10701 is merged.
Thanks On Thu, Nov 10, 2022 at 12:52 PM David Handermann < exceptionfact...@apache.org> wrote: > Joe, > > Thanks for initiating the discussion. I agree with moving toward a 1.19.0 > release instead of 1.18.1 given over 150 Jira issues already tagged with > 1.19.0. > > We should start another thread soon regarding 2.0. One of the key things to > do before that, however, would be to finish adding deprecation logging to > remaining features we plan to remove in 2.0. Having a minor release in > version 1 series deprecating targets for removal should be a prerequisite > before branching and starting on 2.0. > > In the meantime, if that means we plan on a 1.20.0 release, I am in favor > of moving forward with 1.19.0. > > Regards, > David Handermann > > On Thu, Nov 10, 2022 at 1:44 PM Joe Witt <joe.w...@gmail.com> wrote: > > > Team, > > > > We keep getting a slew of emails on various lists, slack, and the > security > > list about commons text. We need a 1.18.1 or a 1.19.0. > > > > Given all that has already happened on 1.19.0 I'm inclined to just 'do > > that' release and get it going. > > > > I know we need to start getting serious about 2.0 but perhaps the most > > realistic path for that is we branch and come back to main after we get > > that figured out. But we need to keep moving forward in the meantime. > > > > Please share if there is anything we know about on the main line which > > would make doing a 1.19.0 problematic. > > > > https://issues.apache.org/jira/projects/NIFI/versions/12352345 > > > > Thanks > > >
