You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by Bryan Bende <bb...@gmail.com> on 2015/07/18 17:21:13 UTC

Next Release

Is the next release going to be 0.2.1 or 0.3.0 ?

Just asking because we would need to add 0.2.1 in JIRA, but also wondering
if the Flume processors being added to develop would warrant going to
0.3.0. I remember we did something similar when adding the Mongo processors
and going from 0.1.0 to 0.2.0, instead of 0.1.1.

-Bryan

Re: Next Release

Posted by Joe Witt <jo...@gmail.com>.
Went ahead and bumped the version to 0.3.0 as what is on develop
already warrants the minor bump.

On Sat, Jul 18, 2015 at 11:34 AM, Joe Witt <jo...@gmail.com> wrote:
> I think it will be 0.3.0.  Was tempted to change last last night when fixing
> incubator markings.  Will do later today unless there are objections.
>
> Id like to see us get a release out pretty quick in this case.
>
> Thanks
> Joe
>
> On Jul 18, 2015 11:21 AM, "Bryan Bende" <bb...@gmail.com> wrote:
>>
>> Is the next release going to be 0.2.1 or 0.3.0 ?
>>
>> Just asking because we would need to add 0.2.1 in JIRA, but also wondering
>> if the Flume processors being added to develop would warrant going to
>> 0.3.0. I remember we did something similar when adding the Mongo
>> processors
>> and going from 0.1.0 to 0.2.0, instead of 0.1.1.
>>
>> -Bryan

Re: Next Release

Posted by Joe Witt <jo...@gmail.com>.
I think it will be 0.3.0.  Was tempted to change last last night when
fixing incubator markings.  Will do later today unless there are objections.

Id like to see us get a release out pretty quick in this case.

Thanks
Joe
On Jul 18, 2015 11:21 AM, "Bryan Bende" <bb...@gmail.com> wrote:

> Is the next release going to be 0.2.1 or 0.3.0 ?
>
> Just asking because we would need to add 0.2.1 in JIRA, but also wondering
> if the Flume processors being added to develop would warrant going to
> 0.3.0. I remember we did something similar when adding the Mongo processors
> and going from 0.1.0 to 0.2.0, instead of 0.1.1.
>
> -Bryan
>