You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Aldrin Piri (JIRA)" <ji...@apache.org> on 2017/09/19 17:03:00 UTC
[jira] [Commented] (MINIFICPP-42) Create separate C++ issue tracker
and migrate issues
[ https://issues.apache.org/jira/browse/MINIFICPP-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16172022#comment-16172022 ]
Aldrin Piri commented on MINIFICPP-42:
--------------------------------------
Will migrate the remainder of the C++ issues but want to first have the MINIFICPP JIRA converted to the appropriate workflow. That request is available here https://issues.apache.org/jira/browse/INFRA-15118
The general logistics of the move are as follows. All C++ component issues and those with a cpp-* fix version prefix have been/will be migrated to the MINIFICPP project.
I have created versions in the MINIFICPP project without the "cpp-" prefix and map these versions upon the Bulk operation in JIRA. JIRA handles the linking of old MINIFI issues to the new MINIFICPP issues.
> Create separate C++ issue tracker and migrate issues
> ----------------------------------------------------
>
> Key: MINIFICPP-42
> URL: https://issues.apache.org/jira/browse/MINIFICPP-42
> Project: NiFi MiNiFi C++
> Issue Type: Task
> Reporter: Aldrin Piri
> Assignee: Aldrin Piri
>
> As per mailing list discussion, a separate issue tracker for the C++ project seems like it would be helpful for maintaining dev efforts.
> Associated conversation located here: https://lists.apache.org/thread.html/3d66e0091040fd0a1025158fef817f45eea7f4aa3ee3ef4cff5d230b@%3Cdev.nifi.apache.org%3E
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)