You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by Marc <ph...@apache.org> on 2018/02/14 18:41:14 UTC
[DISCUSS] Apache NiFi MiNiFi C++ 0.5.0
Hello Everyone,
I wanted to discuss releasing 0.5.0 in the coming weeks. We have some
really useful features and bug fixes in place or nearly up for review. I am
proposing that we release Apache NiFi MiNiFi C++ 0.5.0 when these
activities are complete.
We've had some very useful processors added (UpdateAttribute added
RouteOnAttribute coming ) , MQTT security, support for SUSE/SLES, C2
updates, and various bug fixes. If everyone is favorable to begin the
release process I am happy to act as RM if no one else is interested.
Thanks for your consideration,
Marc
Re: [DISCUSS] Apache NiFi MiNiFi C++ 0.5.0
Posted by Marc <ph...@apache.org>.
Jeremy,
All issues in 0.5.0 have been resolved. Thanks!
On Wed, May 23, 2018 at 4:00 PM, Jeremy Dyer <jd...@gmail.com> wrote:
>
>
>
>
>
>
>
> No problem. Let me know when you get that PR merged in and I’ll kick off the release process
>
>
>
> Thanks - Jeremy Dyer
>
>
>
>
>
> On Wed, May 23, 2018 at 1:20 PM -0400, "Marc" <ph...@apache.org> wrote:
>
>
>
>
>
>
>
>
>
>
> Jeremy,
> Thanks for stepping up!
>
> Aldrin,
> I moved one ticket over that should be in 0.5.0 for which a PR
> exists. Aside from that we should be good to go when that is merged.
>
> On Wed, May 23, 2018 at 11:15 AM, Andy Christianson
> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>>> Sounds great and I think we've gotten some important changes into the
>>> codebase from when this first started. Do we have all the
>>> appropriate/needed issues tagged for this release?
>>
>> I support this release.
>>
>> For this release, I would like to bring special attention to MINIFICPP-281,
>> which has been marked "RESOLVED." In order for that to work, whoever builds the
>> .tar.gz should build the binary with all static linking options enabled, which
>> will minimize dependencies on libraries which may only be on the packager's
>> system, while maximizing portability of the tarball release.
>>
>> Regards,
>>
>> Andy I.C.
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v2.0.22 (GNU/Linux)
>>
>> iQEcBAEBAgAGBQJbBYVvAAoJEG1+mBKNMpIDH9sH/jnbw3hqxBVSZcZwimy2bmEN
>> P64YR3k6Q+OT2pCIp3e88aAHLLy3KUGlZiltp7viiAiNIcHFAmEkbUfpsDEZB6On
>> EyZJMV1NhEx3zDgapfhY3BUcarOgOjL77ZcVCuw3OU0LAkZFrXxG7Ok9YTY2smP8
>> ve4Geck/O8aCtGL5hnNHecJGrm7KsVKbpUeutvwMMTLMNOPwv7ukxLp0o6QufR54
>> cA0nIPJmLrbuCOWWJzSAzLXHu3Wzox9UQ9htNOHgqmzYCAEpMDZrHGE5xJs9K3Iy
>> tLVRebJdQfvH+woKWzmwsqrgf3mSoY2iohza/46Tu3+OvETvVtS44RnFz3paKek=
>> =WN7S
>> -----END PGP SIGNATURE-----
>>
>> Sent from ProtonMail, Swiss-based encrypted email.
>
>
>
>
>
Re: [DISCUSS] Apache NiFi MiNiFi C++ 0.5.0
Posted by Jeremy Dyer <jd...@gmail.com>.
No problem. Let me know when you get that PR merged in and I’ll kick off the release process
Thanks - Jeremy Dyer
On Wed, May 23, 2018 at 1:20 PM -0400, "Marc" <ph...@apache.org> wrote:
Jeremy,
Thanks for stepping up!
Aldrin,
I moved one ticket over that should be in 0.5.0 for which a PR
exists. Aside from that we should be good to go when that is merged.
On Wed, May 23, 2018 at 11:15 AM, Andy Christianson
wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>> Sounds great and I think we've gotten some important changes into the
>> codebase from when this first started. Do we have all the
>> appropriate/needed issues tagged for this release?
>
> I support this release.
>
> For this release, I would like to bring special attention to MINIFICPP-281,
> which has been marked "RESOLVED." In order for that to work, whoever builds the
> .tar.gz should build the binary with all static linking options enabled, which
> will minimize dependencies on libraries which may only be on the packager's
> system, while maximizing portability of the tarball release.
>
> Regards,
>
> Andy I.C.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.22 (GNU/Linux)
>
> iQEcBAEBAgAGBQJbBYVvAAoJEG1+mBKNMpIDH9sH/jnbw3hqxBVSZcZwimy2bmEN
> P64YR3k6Q+OT2pCIp3e88aAHLLy3KUGlZiltp7viiAiNIcHFAmEkbUfpsDEZB6On
> EyZJMV1NhEx3zDgapfhY3BUcarOgOjL77ZcVCuw3OU0LAkZFrXxG7Ok9YTY2smP8
> ve4Geck/O8aCtGL5hnNHecJGrm7KsVKbpUeutvwMMTLMNOPwv7ukxLp0o6QufR54
> cA0nIPJmLrbuCOWWJzSAzLXHu3Wzox9UQ9htNOHgqmzYCAEpMDZrHGE5xJs9K3Iy
> tLVRebJdQfvH+woKWzmwsqrgf3mSoY2iohza/46Tu3+OvETvVtS44RnFz3paKek=
> =WN7S
> -----END PGP SIGNATURE-----
>
> Sent from ProtonMail, Swiss-based encrypted email.
Re: [DISCUSS] Apache NiFi MiNiFi C++ 0.5.0
Posted by Marc <ph...@apache.org>.
Jeremy,
Thanks for stepping up!
Aldrin,
I moved one ticket over that should be in 0.5.0 for which a PR
exists. Aside from that we should be good to go when that is merged.
On Wed, May 23, 2018 at 11:15 AM, Andy Christianson
<ai...@protonmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>> Sounds great and I think we've gotten some important changes into the
>> codebase from when this first started. Do we have all the
>> appropriate/needed issues tagged for this release?
>
> I support this release.
>
> For this release, I would like to bring special attention to MINIFICPP-281,
> which has been marked "RESOLVED." In order for that to work, whoever builds the
> .tar.gz should build the binary with all static linking options enabled, which
> will minimize dependencies on libraries which may only be on the packager's
> system, while maximizing portability of the tarball release.
>
> Regards,
>
> Andy I.C.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.22 (GNU/Linux)
>
> iQEcBAEBAgAGBQJbBYVvAAoJEG1+mBKNMpIDH9sH/jnbw3hqxBVSZcZwimy2bmEN
> P64YR3k6Q+OT2pCIp3e88aAHLLy3KUGlZiltp7viiAiNIcHFAmEkbUfpsDEZB6On
> EyZJMV1NhEx3zDgapfhY3BUcarOgOjL77ZcVCuw3OU0LAkZFrXxG7Ok9YTY2smP8
> ve4Geck/O8aCtGL5hnNHecJGrm7KsVKbpUeutvwMMTLMNOPwv7ukxLp0o6QufR54
> cA0nIPJmLrbuCOWWJzSAzLXHu3Wzox9UQ9htNOHgqmzYCAEpMDZrHGE5xJs9K3Iy
> tLVRebJdQfvH+woKWzmwsqrgf3mSoY2iohza/46Tu3+OvETvVtS44RnFz3paKek=
> =WN7S
> -----END PGP SIGNATURE-----
>
> Sent from ProtonMail, Swiss-based encrypted email.
Re: [DISCUSS] Apache NiFi MiNiFi C++ 0.5.0
Posted by Andy Christianson <ai...@protonmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Sounds great and I think we've gotten some important changes into the
> codebase from when this first started. Do we have all the
> appropriate/needed issues tagged for this release?
I support this release.
For this release, I would like to bring special attention to MINIFICPP-281,
which has been marked "RESOLVED." In order for that to work, whoever builds the
.tar.gz should build the binary with all static linking options enabled, which
will minimize dependencies on libraries which may only be on the packager's
system, while maximizing portability of the tarball release.
Regards,
Andy I.C.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQEcBAEBAgAGBQJbBYVvAAoJEG1+mBKNMpIDH9sH/jnbw3hqxBVSZcZwimy2bmEN
P64YR3k6Q+OT2pCIp3e88aAHLLy3KUGlZiltp7viiAiNIcHFAmEkbUfpsDEZB6On
EyZJMV1NhEx3zDgapfhY3BUcarOgOjL77ZcVCuw3OU0LAkZFrXxG7Ok9YTY2smP8
ve4Geck/O8aCtGL5hnNHecJGrm7KsVKbpUeutvwMMTLMNOPwv7ukxLp0o6QufR54
cA0nIPJmLrbuCOWWJzSAzLXHu3Wzox9UQ9htNOHgqmzYCAEpMDZrHGE5xJs9K3Iy
tLVRebJdQfvH+woKWzmwsqrgf3mSoY2iohza/46Tu3+OvETvVtS44RnFz3paKek=
=WN7S
-----END PGP SIGNATURE-----
Sent from ProtonMail, Swiss-based encrypted email.
Re: [DISCUSS] Apache NiFi MiNiFi C++ 0.5.0
Posted by Aldrin Piri <al...@gmail.com>.
Sounds great and I think we've gotten some important changes into the
codebase from when this first started. Do we have all the
appropriate/needed issues tagged for this release?
https://issues.apache.org/jira/browse/MINIFICPP-420?jql=project%20%3D%20MINIFICPP%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%200.5.0
On Tue, May 22, 2018 at 11:00 AM, Jeremy Dyer <jd...@gmail.com> wrote:
>
>
>
>
>
>
>
> I’m happy to handle RM duties
>
>
>
> Thanks - Jeremy Dyer
>
>
>
>
>
> On Tue, May 22, 2018 at 10:25 AM -0400, "Marc" <ph...@apache.org>
> wrote:
>
>
>
>
>
>
>
>
>
>
> Reviving this thread -- Sorry for the delay. I will start the release
> process with the completion of [1], likely in the next few days or
> early next week. I will take RM duties unless someone else would like
> to take that opportunity.
>
> [1] https://issues.apache.org/jira/browse/MINIFICPP-457
>
> Thanks,
> Marc
>
> On Sun, Feb 18, 2018 at 9:17 AM, Joe Witt wrote:
> > sounds good!
> >
> > On Feb 18, 2018 9:15 AM, "Kevin Doran" wrote:
> >
> >> Hi Marc,
> >>
> >> Thanks for kicking off this discuss thread. I agree we should start
> >> planning the next release to get these new and improved capabilities
> into a
> >> stable version for users.
> >>
> >> Thanks!
> >> Kevin
> >>
> >> On 2/14/18, 13:42, "Marc" wrote:
> >>
> >> Hello Everyone,
> >> I wanted to discuss releasing 0.5.0 in the coming weeks. We have
> some
> >> really useful features and bug fixes in place or nearly up for
> review.
> >> I am
> >> proposing that we release Apache NiFi MiNiFi C++ 0.5.0 when these
> >> activities are complete.
> >>
> >> We've had some very useful processors added (UpdateAttribute
> added
> >> RouteOnAttribute coming ) , MQTT security, support for SUSE/SLES, C2
> >> updates, and various bug fixes. If everyone is favorable to begin
> the
> >> release process I am happy to act as RM if no one else is
> interested.
> >> Thanks for your consideration,
> >> Marc
> >>
> >>
> >>
> >>
>
>
>
>
>
>
Re: [DISCUSS] Apache NiFi MiNiFi C++ 0.5.0
Posted by Jeremy Dyer <jd...@gmail.com>.
I’m happy to handle RM duties
Thanks - Jeremy Dyer
On Tue, May 22, 2018 at 10:25 AM -0400, "Marc" <ph...@apache.org> wrote:
Reviving this thread -- Sorry for the delay. I will start the release
process with the completion of [1], likely in the next few days or
early next week. I will take RM duties unless someone else would like
to take that opportunity.
[1] https://issues.apache.org/jira/browse/MINIFICPP-457
Thanks,
Marc
On Sun, Feb 18, 2018 at 9:17 AM, Joe Witt wrote:
> sounds good!
>
> On Feb 18, 2018 9:15 AM, "Kevin Doran" wrote:
>
>> Hi Marc,
>>
>> Thanks for kicking off this discuss thread. I agree we should start
>> planning the next release to get these new and improved capabilities into a
>> stable version for users.
>>
>> Thanks!
>> Kevin
>>
>> On 2/14/18, 13:42, "Marc" wrote:
>>
>> Hello Everyone,
>> I wanted to discuss releasing 0.5.0 in the coming weeks. We have some
>> really useful features and bug fixes in place or nearly up for review.
>> I am
>> proposing that we release Apache NiFi MiNiFi C++ 0.5.0 when these
>> activities are complete.
>>
>> We've had some very useful processors added (UpdateAttribute added
>> RouteOnAttribute coming ) , MQTT security, support for SUSE/SLES, C2
>> updates, and various bug fixes. If everyone is favorable to begin the
>> release process I am happy to act as RM if no one else is interested.
>> Thanks for your consideration,
>> Marc
>>
>>
>>
>>
Re: [DISCUSS] Apache NiFi MiNiFi C++ 0.5.0
Posted by Marc <ph...@apache.org>.
Reviving this thread -- Sorry for the delay. I will start the release
process with the completion of [1], likely in the next few days or
early next week. I will take RM duties unless someone else would like
to take that opportunity.
[1] https://issues.apache.org/jira/browse/MINIFICPP-457
Thanks,
Marc
On Sun, Feb 18, 2018 at 9:17 AM, Joe Witt <jo...@gmail.com> wrote:
> sounds good!
>
> On Feb 18, 2018 9:15 AM, "Kevin Doran" <kd...@apache.org> wrote:
>
>> Hi Marc,
>>
>> Thanks for kicking off this discuss thread. I agree we should start
>> planning the next release to get these new and improved capabilities into a
>> stable version for users.
>>
>> Thanks!
>> Kevin
>>
>> On 2/14/18, 13:42, "Marc" <ph...@apache.org> wrote:
>>
>> Hello Everyone,
>> I wanted to discuss releasing 0.5.0 in the coming weeks. We have some
>> really useful features and bug fixes in place or nearly up for review.
>> I am
>> proposing that we release Apache NiFi MiNiFi C++ 0.5.0 when these
>> activities are complete.
>>
>> We've had some very useful processors added (UpdateAttribute added
>> RouteOnAttribute coming ) , MQTT security, support for SUSE/SLES, C2
>> updates, and various bug fixes. If everyone is favorable to begin the
>> release process I am happy to act as RM if no one else is interested.
>> Thanks for your consideration,
>> Marc
>>
>>
>>
>>
Re: [DISCUSS] Apache NiFi MiNiFi C++ 0.5.0
Posted by Joe Witt <jo...@gmail.com>.
sounds good!
On Feb 18, 2018 9:15 AM, "Kevin Doran" <kd...@apache.org> wrote:
> Hi Marc,
>
> Thanks for kicking off this discuss thread. I agree we should start
> planning the next release to get these new and improved capabilities into a
> stable version for users.
>
> Thanks!
> Kevin
>
> On 2/14/18, 13:42, "Marc" <ph...@apache.org> wrote:
>
> Hello Everyone,
> I wanted to discuss releasing 0.5.0 in the coming weeks. We have some
> really useful features and bug fixes in place or nearly up for review.
> I am
> proposing that we release Apache NiFi MiNiFi C++ 0.5.0 when these
> activities are complete.
>
> We've had some very useful processors added (UpdateAttribute added
> RouteOnAttribute coming ) , MQTT security, support for SUSE/SLES, C2
> updates, and various bug fixes. If everyone is favorable to begin the
> release process I am happy to act as RM if no one else is interested.
> Thanks for your consideration,
> Marc
>
>
>
>
Re: [DISCUSS] Apache NiFi MiNiFi C++ 0.5.0
Posted by Kevin Doran <kd...@apache.org>.
Hi Marc,
Thanks for kicking off this discuss thread. I agree we should start planning the next release to get these new and improved capabilities into a stable version for users.
Thanks!
Kevin
On 2/14/18, 13:42, "Marc" <ph...@apache.org> wrote:
Hello Everyone,
I wanted to discuss releasing 0.5.0 in the coming weeks. We have some
really useful features and bug fixes in place or nearly up for review. I am
proposing that we release Apache NiFi MiNiFi C++ 0.5.0 when these
activities are complete.
We've had some very useful processors added (UpdateAttribute added
RouteOnAttribute coming ) , MQTT security, support for SUSE/SLES, C2
updates, and various bug fixes. If everyone is favorable to begin the
release process I am happy to act as RM if no one else is interested.
Thanks for your consideration,
Marc