+1 binding Edward,
If you could provide some additional details in a new thread, that would be helpful. As stated, the primary purpose of the proposed goals is to reduce technical debt without introducing too many breaking changes. Depending on the components in question, there may be opportunity for some refactoring. Regards, David Handermann On Wed, Dec 14, 2022 at 3:27 PM Zoltán Kornél Török <taz19880...@gmail.com> wrote: > +1 (non-binding) > > Nathan Gough <thena...@apache.org> ezt írta (időpont: 2022. dec. 14., Sze, > 20:46): > > > +1 (binding) > > > > The proposal sounds great to me > > > > > > > > On Wed, Dec 14, 2022, 1:01 PM Edward Armes <edward.ar...@gmail.com> > wrote: > > > > > -1 (non-binding) > > > > > > Im not sure if this is covered by 8 and 5 , but I would like to suggest > > > that as part of 2.0 focus on removing places were concrete > > implementations > > > are used over interfaces, and update the way the website docs are > > generated > > > to ensure that NARs that not included in the standard distribution are > > > included. > > > > > > I think this would allow for work of a NAR registry to happen outside > of > > a > > > major release and allow for the potential consideration of individually > > > versions components reducing the sizes of future releases. > > > > > > Edward > > > > > > > > > On Mon, 12 Dec 2022, 20:32 Andrew Lim, <andrewlim.apa...@gmail.com> > > wrote: > > > > > > > +1 (binding) > > > > > > > > > On Dec 12, 2022, at 12:02 PM, David Handermann < > > > > exceptionfact...@apache.org> wrote: > > > > > > > > > > Team, > > > > > > > > > > Following positive feedback on NiFi 2.0 Proposed Release Goals [1] > on > > > the > > > > > recent discussion thread [2], I am calling this vote to adopt the > > > > following > > > > > as Release Goals for NiFi 2.0: > > > > > > > > > > 1. Remove Java 8 support and require Java 11 > > > > > 2. Remove deprecated components > > > > > 3. Remove deprecated component properties > > > > > 4. Remove components integrating with unmaintained services > > > > > 5. Remove compatibility classes and methods > > > > > 6. Remove flow.xml.gz in favor of flow.json.gz > > > > > 7. Remove duplicative features > > > > > 8. Upgrade internal Java API references > > > > > 9. Reorganize standard components > > > > > 10. Implement migration tools for upgrading flows > > > > > > > > > > A positive vote indicates agreement on these goals and the > initiation > > > of > > > > > the following actions: > > > > > > > > > > 1. Rename NiFi 2.0 Proposed Release Goals to NiFi 2.0 Release Goals > > > > > 2. Create version 1 branch in Git for subsequent support releases > on > > > the > > > > > version 1 series > > > > > 3. Update the current main branch in Git to version 2.0.0-SNAPSHOT > > > > > > > > > > The vote will be open for 72 hours and follow standard procedures > for > > > > > release votes. > > > > > > > > > > Please review the linked goals and discussions for background. > > > > > > > > > > [ ] +1 Adopt NiFi 2.0 Release Goals > > > > > [ ] +0 No opinion > > > > > [ ] -1 Do not adopt NiFi 2.0 Release Goals for the following > > reasons... > > > > > > > > > > [1] > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/NiFi+2.0+Proposed+Release+Goals > > > > > [2] > https://lists.apache.org/thread/xo77p9t3xg4k70356xrqbdg4m9sg7sf8 > > > > > > > > > > > > > > > > -- > Üdvözlettel, > Török Zoltán Kornél > 06-30-509-0541 >
