If we don't create a project, I"m guessing the label would serve to reduce the number of unlabeled tickets by virtue of having some labeled as JAVA? It seems that without separate projects we won't eliminate the problem, entirely. It's a ticket creation issue, one of which I know I've caused at some point. It seems a separate project is the most likely to yield the desired result...
On Mon, Aug 21, 2017 at 11:10 AM, Joe Witt <joe.w...@gmail.com> wrote: > 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 can ask ASF infra to setup another JIRA project such > as 'minificpp' but I'd like to avoid that until we're really sure we > want to bug em. > > Thanks > > On Mon, Aug 21, 2017 at 11:03 AM, Andy Christianson > <achristian...@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: Friday, August 18, 2017 2:56 PM > > To: dev@nifi.apache.org > > Subject: Separate MiNiFi projects in JIRA > > > > 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 > > so a useful filter is hard to make.) Has there been any consideration > given > > to having separate JIRA projects for the C++/Java MiNiFi implementations? > > > > Thanks, > > Jeff > > > > >
