Team,
After a successful discussion here [1] and JIRA here [2] and proposed PR
[3] I'd like to codify this in a vote.
It appears we've not actually voted on any NIPs yet so I'll conduct this
vote with 'lazy consensus' [4].
I'll leave this open for 3 days and if nobody objects will consider the N
May not be up to date but here is some useful documentation:
https://cwiki.apache.org/confluence/display/NIFI/For+Developers
The TLDR is: you fork NiFi, you create a branch for your work on your fork
(usually named with the NIFI JIRA reference), you push your commits there
and then you open a pull
Hello
You can create pull requests.
Commit access comes at a later stage once earning committer status.
Thanks!
Joe
On Thu, Mar 20, 2025 at 3:15 PM Tomasz Korniszuk
wrote:
> Good evening
>
> Can I also get access push commits to github for user TomaszK-stack?
>
> Best regards,
>
> Tomasz Ko
Team,
I am pleased to be calling this vote for the source release of Apache
NiFi API 2.1.0.
Please review the following guide for how to verify a release candidate build:
https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification+for+NiFi+API
The source being voted on the a
+1, thanks for putting this together Mark
Le ven. 4 avr. 2025 à 22:17, Mark Payne a écrit :
>
> Team,
>
> After a successful discussion on JIRA here [1] I'd like to codify this in a
> vote.
>
> Following set precedence for NIPs, I'll conduct this vote with 'lazy
> consensus’ [2].
>
> I'll leave
