nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Witt <joe.w...@gmail.com>
Subject Re: prepare for apache nifi 0.0.2 incubating?
Date Mon, 09 Mar 2015 14:17:38 GMT
Ok all things look good.  Sounds like items raised are addresses or in
a later release.  Starting the process to put together nifi 0.0.2
(incubating) RC1.

Thanks
Joe

On Wed, Mar 4, 2015 at 3:47 PM, Jennifer Barnabee
<jennifer.barnabee@gmail.com> wrote:
> Ok, no problem. Thanks for resolving that one. I found this page:
>
> https://issues.apache.org/jira/secure/Dashboard.jspa
>
> It says, "Only developers can edit, prioritize, schedule and resolve
> issues."
>
> -Jenn
>
> On Wed, Mar 4, 2015 at 3:16 PM, Mark Payne <markap14@hotmail.com> wrote:
>
>> Jenn,
>>
>>
>> Honestly, I have no idea. I can mark it resolved. I’m guessing that you
>> need a higher level permission?
>>
>>
>>
>>
>>
>>
>> From: Jennifer Barnabee
>> Sent: ‎Wednesday‎, ‎March‎ ‎4‎, ‎2015 ‎1‎:‎54‎ ‎PM
>> To: dev@nifi.incubator.apache.org
>>
>>
>>
>>
>>
>> Hi Mark,
>> I would resolve NIFI-370, but I don't seem to have that option.
>> I've been able to resolve the issues that I've created. But I don't seem to
>> have that ability on tickets created by others. Do you think I set up my
>> account wrong? Or is this something you guys can control?
>> Thanks.
>> -Jenn
>>
>> On Wed, Mar 4, 2015 at 1:34 PM, Mark Payne <markap14@hotmail.com> wrote:
>>
>> > Dan,
>> >
>> > I think if you know which version it will go into, you can add the fix
>> > version when you create the issue. Otherwise, it should be set when the
>> > ticket is marked as resolved -- and I think this should be done by
>> > whichever committer merges the code into the develop branch.
>> >
>> > Thanks
>> > -Mark
>> >
>> > > From: dbress@onyxconsults.com
>> > > To: dev@nifi.incubator.apache.org
>> > > Subject: Re: prepare for apache nifi 0.0.2 incubating?
>> > > Date: Wed, 4 Mar 2015 15:04:43 +0000
>> > >
>> > > On the subject of tickets that are actually fixed and merged into
>> > develop, but not updated in JIRA: Who is responsible for setting the fix
>> > version and the status?  The person who originally created the ticket?
>> The
>> > person who made the fix?  The person who merged the fix?  Or?
>> > >
>> > > This ticket falls into that category: NIFI-370
>> > >
>> > > Dan Bress
>> > > Software Engineer
>> > > ONYX Consulting Services
>> > >
>> > > ________________________________________
>> > > From: Dan Bress <dbress@onyxconsults.com>
>> > > Sent: Wednesday, March 4, 2015 8:32 AM
>> > > To: dev@nifi.incubator.apache.org
>> > > Subject: Re: prepare for apache nifi 0.0.2 incubating?
>> > >
>> > > Joe,
>> > >     I just updated the status of one ticket(NIFI-344) to reflect that
>> it
>> > was committed and merged into 0.0.2.
>> > >    The same thing applies to NIFI-333, but I am not the owner/reporter
>> > so I cannot update the status or fix version.  Can you do that?
>> > >
>> > >     I am not aware of anything else I'd like to see in 0.0.2.
>> > >
>> > > Dan Bress
>> > > Software Engineer
>> > > ONYX Consulting Services
>> > >
>> > > ________________________________________
>> > > From: Joe Witt <joe.witt@gmail.com>
>> > > Sent: Tuesday, March 3, 2015 10:11 PM
>> > > To: dev@nifi.incubator.apache.org
>> > > Subject: prepare for apache nifi 0.0.2 incubating?
>> > >
>> > > Hello
>> > >
>> > > The tickets assigned to 0.0.2 have winded down and things look pretty
>> > > well staged to prepare for a release.  We have some PRs outstanding
>> > > but nothing that appears to need to go in immediately and/or is
>> > > waiting on 0.1.0 which is likely the next release after this (due to
>> > > some breaking changes coming to support runtime mods to controller
>> > > tasks/reporting tasks)
>> > >
>> > > Anyone have anything else they want to see in 0.0.2?
>> > >
>> > > Thanks
>> > > Joe
>> >

Mime
View raw message