Re: Next release NiFi 1.12

Here is the discussion thread [1]. [1] https://lists.apache.org/thread.html/r2cfeda59f96613c9d1739f4f2a1fd83ab15a4ff77d4659154a45bcac%40%3Cdev.nifi.apache.org%3E Andy

Re: Next release NiFi 1.12

Martin Youll need to subscribe to dev to see this but there is already a discuss thread for it. As I mentioned on slack we just need to do it. There was some items folks were trying to wrap. Thanks On Thu, Jul 2, 2020 at 6:20 AM Martin Ebert wrote: > Hi community, > there are so many great

Re: Next Release of Apache Nifi

Thanks Joe for the update !! On Tue, Feb 9, 2016 at 9:03 PM, Joe Percivall < joeperciv...@yahoo.com.invalid> wrote: > Hello Shweta, > > Sorry no has responded to you, but if you have seen the recent activity in > the Dev user list, we are currently working on cutting a release for 0.5.0. > There

Re: Next Release of Apache Nifi

Hello Shweta, Sorry no has responded to you, but if you have seen the recent activity in the Dev user list, we are currently working on cutting a release for 0.5.0. There is a preliminary Release Client if you'd like to take a look and give some feedback! Joe - - - - - - Joseph Percivall

Re: Next Release of Apache Nifi

Shweta, Here is the dev list email that Joe is referring to: http://mail-archives.apache.org/mod_mbox/nifi-dev/201602.mbox/%3CCA%2BLyY54edrdoxHtpksRyOhCq8hYVgDFx3c4ZCzHcyk3%3D%3D9qx%2Bw%40mail.gmail.com%3E We found a couple of issues that are still being worked, but I expect another release

Re: Next release?

Original Message- >> From: Joe Witt [mailto:joe.w...@gmail.com] >> Sent: Monday, November 02, 2015 8:56 AM >> To: dev@nifi.apache.org >> Subject: Re: Next release? >> >> Team...we def need to address or move a good bit of ticketage to move >> towards an RC. It i

Re: Next release?

ould >>>> do. We obviously can't test all the things and environments and so on >>> with >>>> this model. The more CI we can get established the better we can do. >>> But >>>> we have much room for improvement in validating releases. >>>

Re: Next release?

s are of course run by the builds but we rely on people > power to > >>>> verify system level testing and that is part of that testing folks > should > >>>> do. We obviously can't test all the things and environments and so on > >>> with > >&g

Re: Next release?

> Joe > > > >>> > > > >>>> On Mon, Nov 2, 2015 at 3:06 PM, Joe Witt <joe.w...@gmail.com> > > wrote: > > > >>>> The current process is outlined in our release guide. But the > main > > > idea > > > >>> is &g

Re: Next release?

> > >>> I'll keep pairing down the tickets on 040 and pinging folks to > > > > >>> understand likely target dates for completion. > > > > >>> > > > > >>> Thanks > > > > >>> Joe > > > > >>> > >

Re: Next release?

Mon, Nov 2, 2015 at 3:06 PM, Joe Witt <joe.w...@gmail.com> wrote: >>>>>> The current process is outlined in our release guide. But the main >> idea >>>>> is >>>>>> that all who wish to participate in release validation do so from the >> RC. >

Re: Next release?

t; of 040. > > > > > >>> > > > > > >>> We released 0.3.0 on Sep 19th. I suggest we try to target Nov > > 19th > > > > > >>> then for 0.4.0. There is already quite a lot in this and so I > > > think > > > > > >>> we should get

Re: Next release?

which > > > > > > >>> are unresolved. I reassigned many but still many remain. > > Please > > > > do > > > > > a > > > > > > >>> scan through if you reported them and see which ones can be > > moved > > > > off > &

RE: Next release?

[mailto:joe.w...@gmail.com] Sent: Monday, November 02, 2015 8:56 AM To: dev@nifi.apache.org Subject: Re: Next release? Team...we def need to address or move a good bit of ticketage to move towards an RC. It isn't critical we do it 'now' but we should strive for 6 to 8 week release cycles in my view. We

RE: Next release?

ginal Message- > From: Joe Witt [mailto:joe.w...@gmail.com] > Sent: Monday, November 02, 2015 8:56 AM > To: dev@nifi.apache.org > Subject: Re: Next release? > > Team...we def need to address or move a good bit of ticketage to move > towards an RC. It isn't critical we do it

Re: Next release?

All, On an extremely busy cluster that I work with, I've noticed some thread starvation issues on the NCM. It manifests as the "spinning wheel of death" when refreshing the NiFi UI. Thread and heap dumps point to the WebClusterManager in the framework. I've made some small quick-win changes