Sounds like a plan. When someone picks it up let me know and I will supply the users with test builds to get some user feedback to whoever picks it up. On Tue, Jun 19, 2018 at 1:15 PM Andy LoPresto <[email protected]> wrote:
> Hi Mike, > > I think that’s a great user request and something that requires > substantial discussion because it has been brought up before. I don’t think > it is worth delaying the release though. MiNiFi Java 0.5.0 needs NiFi to be > released first to gain the benefit of the new processors, etc. With our > always-improving release process, we can make another release soon if the > community feels there is a need for it. Thanks. > > > Andy LoPresto > [email protected] > *[email protected] <[email protected]>* > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > > On Jun 19, 2018, at 10:12 AM, Mike Thomsen <[email protected]> wrote: > > I'm working with a team that's doing some very visible work with the > registry, and one of the leads showed me that if someone even slightly > moves a UI element it registers as a change if the PG is versioned. That's > what they expect, but they'd really like the ability to lock down > components as they're working on them and then be able to lock down an > entire PG once they're done with it. I added a Jira ticket for it here: > > https://issues.apache.org/jira/browse/NIFI-5321 > > I know 1.7.0 is supposed to go up for a release vote soon, but I think this > ticket is a good UX reason to hold off a little. > > Thanks, > > Mike > > >
