Team, The NiFi API has remained relatively unchanged for the first several releases of the NiFi project, highlighting the value of a decoupled release strategy for the public API and the framework. Recent updates to the NiFi API main branch have added the DisallowRunOnce annotation and implemented deterministic ordering for elements of the Runtime Extension Manifest XML.
Although there are several other open NiFi Improvement Proposals that could impact the NiFi API, these have not yet been voted on, and are not ready for implementation. With the changes mentioned above, releasing version 2.1.0 of the NiFi API would make these updates available for integration into subsequent NiFi framework releases. I can handle the Release Manager responsibilities for NiFi API, and I can proceed with preparing a Release Candidate build tomorrow based on feedback. This does raise the need to create an API Compatibility Matrix for NiFi API and NiFi Framework, so I can also put together an initial version in the project Confluence page for tracking current and subsequent releases. Regards, David Handermann
