Ok it is all in. Starting RC build. Please do not tag anything else to
1.19. If necessary I'll pull things in.
1.20 has been established.
Thanks
On Tue, Nov 22, 2022 at 8:51 AM Joe Witt wrote:
> Gonna wait for https://issues.apache.org/jira/browse/NIFI-10857 as this
> was apparently made bi
Gonna wait for https://issues.apache.org/jira/browse/NIFI-10857 as this was
apparently made bigger and some tests broken from another 1.19 JIRA.
Probably gonna kick out the RC tomorrow and then let the vote run through
Monday.
Thanks
On Fri, Nov 18, 2022 at 9:56 AM Mike Thomsen wrote:
> Can so
Can someone do a quick review on this? I think it would be a nice
little bullet point on our release to say we added preliminary support
for Neo4J 5 since it's so new.
https://github.com/apache/nifi/pull/6684
(Enabling the V5 profile has a hard dependency on Java 17)
On Fri, Nov 18, 2022 at 11:0
Goodness. Some pretty cool collaboration on things like the docker updates
and NiFi 1.19 is looking healthy. Time permitting, I'd like to start the
RC today.
Thanks
On Tue, Nov 15, 2022 at 6:16 PM Kevin Doran wrote:
> NIFI-10701 is merged. If folks are ok holding off a day or two more for
>
NIFI-10701 is merged. If folks are ok holding off a day or two more for
1.19, I'll look into following the work Ferenc Kis did for that to knock
out NIFI-10820.
On Nov 15, 2022 at 19:43:57, Matt Burgess wrote:
> Awesome, thanks all! I'd like to wait for Github actions to be happy
> and then mer
Awesome, thanks all! I'd like to wait for Github actions to be happy
and then merge?
On Tue, Nov 15, 2022 at 7:11 PM Mark Bean wrote:
>
> NIFI-10703 has been worked through. I think it's good to go now.
>
> On Tue, Nov 15, 2022 at 4:43 PM Matt Burgess wrote:
>
> > I can take that review too, if
NIFI-10703 has been worked through. I think it's good to go now.
On Tue, Nov 15, 2022 at 4:43 PM Matt Burgess wrote:
> I can take that review too, if your suggestions are incorporated. I
> started looking the other day but didn't get to dig in. I'll try to
> reproduce in the meantime.
>
> Regard
I can take that review too, if your suggestions are incorporated. I
started looking the other day but didn't get to dig in. I'll try to
reproduce in the meantime.
Regards,
Matt
On Tue, Nov 15, 2022 at 4:42 PM Nathan Gough wrote:
>
> We might also want https://issues.apache.org/jira/browse/NIFI-1
We might also want https://issues.apache.org/jira/browse/NIFI-10787
On Tue, Nov 15, 2022 at 4:05 PM Mark Bean wrote:
> I will be on it in about 2 hours, if not addressed sooner.
>
> On Tue, Nov 15, 2022 at 3:46 PM Joe Witt wrote:
>
> > NIFI-10703 would be great to get in. Just a matter of gett
Mark,
I can review any incoming changes when they land, if that helps.
Regards,
Matt
On Tue, Nov 15, 2022 at 4:05 PM Mark Bean wrote:
>
> I will be on it in about 2 hours, if not addressed sooner.
>
> On Tue, Nov 15, 2022 at 3:46 PM Joe Witt wrote:
>
> > NIFI-10703 would be great to get in. J
I will be on it in about 2 hours, if not addressed sooner.
On Tue, Nov 15, 2022 at 3:46 PM Joe Witt wrote:
> NIFI-10703 would be great to get in. Just a matter of gettin' it done and
> merged I think. You're on it?
>
> Thanks
>
> On Tue, Nov 15, 2022 at 1:38 PM Mark Bean wrote:
>
> > Sorry..
NIFI-10703 would be great to get in. Just a matter of gettin' it done and
merged I think. You're on it?
Thanks
On Tue, Nov 15, 2022 at 1:38 PM Mark Bean wrote:
> Sorry.. check that. There's a typo in the latest commit on that PR.
>
> On Tue, Nov 15, 2022 at 3:35 PM Mark Bean wrote:
>
> > Cou
Sorry.. check that. There's a typo in the latest commit on that PR.
On Tue, Nov 15, 2022 at 3:35 PM Mark Bean wrote:
> Could we get NIFIDEVS-10703 (PR #6638) in there too? AFAIK, it's good to
> go.
>
> Thanks,
> Mark
>
>
> On Tue, Nov 15, 2022 at 2:56 PM Joe Witt wrote:
>
>> Hello All,
>>
>> I
Could we get NIFIDEVS-10703 (PR #6638) in there too? AFAIK, it's good to go.
Thanks,
Mark
On Tue, Nov 15, 2022 at 2:56 PM Joe Witt wrote:
> 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 1
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
> relea
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 deprecatio
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 pe
17 matches
Mail list logo
