Hi Dan, I'm probably supposed to close this ticket. My access to JIRA doesn't seem to allow me to close tickets; however, I could be just missing something.
Is there something I need to do to change my access level? Thanks. -Jenn On Wed, Mar 4, 2015 at 10:04 AM, Dan Bress <[email protected]> wrote: > 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 <[email protected]> > Sent: Wednesday, March 4, 2015 8:32 AM > To: [email protected] > 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 <[email protected]> > Sent: Tuesday, March 3, 2015 10:11 PM > To: [email protected] > 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 >
