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 <jdy...@gmail.com> wrote:

>
>
>
>
>
>
>
>                 I’m happy to handle RM duties
>
>
>
>                 Thanks - Jeremy Dyer
>
>
>
>
>
> On Tue, May 22, 2018 at 10:25 AM -0400, "Marc" <phroc...@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
> >>
> >>
> >>
> >>
>
>
>
>
>
>

Reply via email to