er
> > >> > these
> > >> > > ASF JIRA projects (Aldrin?).
> > >> > > >
> > >> > > > -Kevin
> > >> > > >
> > >> > > > On 8/21/17, 15:00, "Jeff Zemerick" <
> > > On 8/21/17, 15:00, "Jeff Zemerick" <jzemer...@apache.org>
> >> wrote:
> >> > > >
> >> > > > Would it be possible to use a JIRA custom field
> (that's
> >> required)
> >> > > called
> &
d with
>> choices of C++
>> > > and Java?
>> > > > With more than just Java and C++ for components I'm
>> afraid those
>> > two
>> > > > choices might be overlooked when
> > > > Making it required sounds like an improvement, at the very
least.
> > > >
> > > > -Andy I.C.
> > > >
> > > > From: Kevin Doran <kd
> > achristian...@hortonworks.com> wrote:
> >
> > > Making it required sounds like an improvement, at the very least.
> > >
> > > -Andy I.C.
> > > ________
> > > From: Kevin Doran <kdoran.apa...@gmail.com>
> >
st.
> > >
> > > -Andy I.C.
> > > ________
> > > From: Kevin Doran <kdoran.apa...@gmail.com>
> > > Sent: Monday, August 21, 2017 11:22 AM
> > > To: dev@nifi.apache.org
> > >
> From: Kevin Doran <kdoran.apa...@gmail.com>
> Sent: Monday, August 21, 2017 11:22 AM
> To: dev@nifi.apache.org
> Subject: Re: Separate MiNiFi projects in JIRA
>
> Would it suffice to make the existing 'component' field _required_ at
&
nday, August 21, 2017 11:22 AM
> To: dev@nifi.apache.org
> Subject: Re: Separate MiNiFi projects in JIRA
>
> Would it suffice to make the existing 'component' field _required_ at
> ticket creation time, and having components consist of 'C++', 'Java', &
> perhaps 'Both/All/*' as well? I
Making it required sounds like an improvement, at the very least.
-Andy I.C.
From: Kevin Doran <kdoran.apa...@gmail.com>
Sent: Monday, August 21, 2017 11:22 AM
To: dev@nifi.apache.org
Subject: Re: Separate MiNiFi projects in JIRA
Would it suffice t
Sent: Monday, August 21, 2017 11:10 AM
To: dev@nifi.apache.org
Subject: Re: Separate MiNiFi projects in JIRA
Can we recommend and setup a set of component names so that filtering
can be done reasonably?
If we do that would it be sufficient?
Alternatively we
.
From: Joe Witt <joe.w...@gmail.com>
Sent: Monday, August 21, 2017 11:10 AM
To: dev@nifi.apache.org
Subject: Re: Separate MiNiFi projects in JIRA
Can we recommend and setup a set of component names so that filtering
can be done reasonably?
If we do that would it be sufficient?
Alterna
.@hortonworks.com> wrote:
> > Agree 100%. I have been bitten by this a few times. Is this something
> Aldrin can do/have done?
> >
> > -Andy I.C.
> >
> > From: Jeff Zemerick <jzemer...@apache.org>
> > Sent: Frid
Agree 100%. I have been bitten by this a few times. Is this something Aldrin
can do/have done?
-Andy I.C.
From: Jeff Zemerick <jzemer...@apache.org>
Sent: Friday, August 18, 2017 2:56 PM
To: dev@nifi.apache.org
Subject: Separate MiNiFi projects i
The MINIFI project in JIRA is currently a combination of issues for both
the C++ and Java implementations. Some issues for the C++ project do have
the C++ component set but some don't and it can sometimes be hard to easily
differentiate the issues by their titles. (There isn't a "Java" component
14 matches
Mail list logo
