Anuj,

We don't make releases for previous release lines of Apache NiFi (besides
1.9.2 is more than one year old). There is an ongoing discussion for
releasing either a 1.11.5 version or a 1.12.0 version. Assuming the pull
request is reviewed and merged before we make this release, then it'd
available as part of this release. It'd be up to you to upgrade to this new
version of Apache NiFi, or backport the fix in your version, or just take
the new NAR and drop it in your version of NiFi.

If you can test the pull request and provide a review on it, that would
certainly help getting it merged faster. You can also open your own pull
requests against the Apache NiFi project. NiFi is an open source project
with an amazing community and we want to make sure that anyone can
contribute to the project (by helping with the documentation, by reviewing
pull requests, by submitting pull requests, by testing release candidates,
by helping debugging issues, etc). This project is moving forward thanks to
the collaborative efforts of everyone. We understand that not everyone is
in a position to submit pull requests, but I do think that anyone can help
on many aspects of the project (not necessarily requiring to write code).
If you have an urgent need for this fix, helping others with their own
needs would likely help. You can see this as an exchange of courtesies.

Thanks for your involvement in the community.

Pierre

Le sam. 23 mai 2020 à 07:10, Anuj Jain <[email protected]> a écrit :

> Hi Mark,
>
> zenfenan, did the code fix raised a PR
> https://github.com/apache/nifi/pull/4290/commits
>
> code change seems fine for me, but this is raised for master branch
> as I suggested, we can create a newer version/branch from 1.9.2, and fix
> that code there and release that
> so it will not impact other latest versions
> once it got tested in our environment then I will confirm and you will
> merge that into master and whenever Nifi new version release this fix will
> be there.
>
> Please revert if have any concern on this.
>
> Regards
> Anuj Jain
>
>
>
>
> ________________________________
>
>
> The information contained in this communication is confidential and
> intended solely for the use of the individual named or entity to whom it is
> addressed and others authorized to receive it. If you are not the intended
> recipient you are hereby notified that any disclosure, copying,
> circulation, distribution or taking any action in reliance on the contents
> of this information is strictly prohibited and may be unlawful. Please
> delete it and any attachments from your systems and notify the sender that
> you have received it in error. Unless stated to the contrary, any opinions
> expressed in this message are personal and may not be attributed to Aeris
> Communications.
>

Reply via email to