All,

If there are no objections, I am volunteering to take release manager
responsibilities for the 0.3.0 release.

This process will include releases for three components:
* nifi-parent, version 1.0.1
* nifi-nar-maven-plugin, version 1.0.2
* nifi, version 0.3.0

A ticket [1] has been created to track the release process.

Thanks!

[1] https://issues.apache.org/jira/browse/NIFI-778



On Mon, Jul 20, 2015 at 7:37 AM, Mark Payne <[email protected]> wrote:

> Ryan,
>
> Yup, I'll make sure that one is in there.
>
> Does anyone else have any ticket that they want to ensure gets out today?
>
> Thanks
> -Mark
>
> ----------------------------------------
> > Date: Mon, 20 Jul 2015 10:33:14 -0400
> > Subject: Re: nifi-0.3.0 release
> > From: [email protected]
> > To: [email protected]
> >
> > Will the Amazon AWS processors fix make this release?
> >
> > On Mon, Jul 20, 2015 at 10:29 AM, Mark Payne <[email protected]>
> wrote:
> >
> >> Joe,
> >>
> >> Not a problem. I updated JIRA to show the tickets that will go into
> 0.3.0.
> >>
> >> Thanks
> >> -Mark
> >>
> >> ----------------------------------------
> >>> Date: Mon, 20 Jul 2015 10:10:20 -0400
> >>> Subject: Re: nifi-0.3.0 release
> >>> From: [email protected]
> >>> To: [email protected]
> >>>
> >>> Sounds good. Would like to see the items that end up on the release
> list
> >>> in jira.
> >>>
> >>> Also we need to put together good release notes this time.
> >>>
> >>> Thanks
> >>> Joe
> >>> On Jul 20, 2015 10:02 AM, "Mark Payne" <[email protected]> wrote:
> >>>
> >>>> Hello all,
> >>>>
> >>>> We have found an issue that is present in nifi 0.2.0 that results in
> new
> >>>> accounts not automatically being requested as they should when a new
> >> user
> >>>> attempts to access an instance of NiFi.
> >>>>
> >>>> This is not a security issue but could cause some headaches for
> >> operators
> >>>> who are running secure instances of NiFi, especially new instances.
> >>>>
> >>>> Unless there are any objections, I would like to go ahead and start
> >>>> putting together an 0.3.0 release that has this issue addressed, the
> new
> >>>> Flume Processors, and any other tickets that are complete and ready to
> >> go.
> >>>> All others will be moved to version 0.4.0.
> >>>>
> >>>> In the absence of any objections, we will probably have a package
> built
> >>>> and ready to be voted on today.
> >>>>
> >>>> Thank you
> >>>> -Mark
> >>>>
> >>>>
> >>
> >>
>
>

Reply via email to