Getting the build artifact Jira in should help drastically with the resource size issues. Will cut our footprint in about half.
Andy LoPresto [email protected] [email protected] PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Oct 3, 2018, at 19:33, Joe Witt <[email protected]> wrote: > > Mike, > > Processors in particularly are among the toughest at this point. We > have very very little headroom on dependency size for the full build > size that we upload to ASF infra and mirrors. That and the license > review work involved in each... > > We should really create a way to publish processors on more frequent, > irregular intervals where the release work and size/etc.. are far less > problematic. We have another discuss thread on that so I'll leave it > there for discussion. I do share your view that this processor (among > several others outstanding) would be really useful but i am definitely > thinking we should keep release pace up. Release more often...release > processors separately, etc.. > > Thanks > Joe >> On Wed, Oct 3, 2018 at 9:30 PM Mike Thomsen <[email protected]> wrote: >> >> I would like to see the Neo4J work that mans2singh is doing get included. >> Being able to at least partially support a popular graph database would be >> a nice feather in our cap. >> >> On Wed, Oct 3, 2018 at 5:12 PM Andy LoPresto <[email protected]> wrote: >> >>> I am currently working on a TLS Toolkit refactor (NIFI-5462 & NIFI-5485) >>> and HashAttribute updates (NIFI-5582). I believe there are a couple upgrade >>> PRs open, and I would really like to see NIFI-5402 (no .tar.gz in the >>> build) tackled for this release as well. >>> >>> >>> Andy LoPresto >>> [email protected] >>> *[email protected] <[email protected]>* >>> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 >>> >>> On Oct 3, 2018, at 11:16 AM, Joe Witt <[email protected]> wrote: >>> >>> Jeff - thanks again for volunteering. I just went through the open >>> items tagged to 1.8.0 to try and shake some loose, close down ones >>> that appear to be done but forgotten, and initiate resolution on one >>> that is in a dangling state. >>> >>> Another very nice release shaping up here. All the work around load >>> balancing and node offloading is awesome. >>> >>> Thanks >>> On Wed, Oct 3, 2018 at 2:06 PM Jeff <[email protected]> wrote: >>> >>> >>> It looks like we're getting close to a point where we could release NiFi >>> 1.8.0The release tracking page for version 1.8.0 [1] shows 3 "in progress" >>> and 9 "to do" issues. In addition to what has been tagged with a fix >>> version of 1.8.0, it looks like NIFI-5516 and NIFI-5585 are close to >>> completion. >>> >>> Are there other JIRAs that the community considers necessary for the >>> release that are close to being resolved, with the goal of getting a >>> release candidate out in the next couple of weeks? >>> >>> I'm happy to perform the release manager duties! >>> >>> [1] https://issues.apache.org/jira/projects/NIFI/versions/12343482 >>> >>> >>>
