That makes sense to me, thanks Gilles
On Sat, Jan 7, 2017 at 7:17 PM, Gilles <gil...@harfang.homelinux.org> wrote:
> On Sat, 7 Jan 2017 18:58:58 -0500, Raymond DeCampo wrote:
>
>> Gilles - would this be the preferred way to handle the split of
>> commons-complex from CM? I could go through the issues and attempt to
>> identify which ones should be moved (I don't think I have permission to
>> actually move them however).
>>
>
> For the sake of traceability, I'd rather recommend to create
> new issues in the Jira's "COMPLEX" and link ("supersedes") them
> to the old one in "MATH" project.
> This would avoid people hitting the same issue in a released
> "commons-math" JAR recreating the report, not knowing about
> a yet unreleased "commons-complex".
> Then, when it is fixed in commons-complex, the report in "MATH"
> will be resolved as "Won't fix".
>
> Regards,
> Gilles
>
>
>
>> On Sat, Jan 7, 2017 at 12:09 PM, Pascal Schumacher <
>> pascalschumac...@gmx.net
>>
>>> wrote:
>>>
>>
>> Yes it is possible. You can move jira issues between projects with "more"
>>> -> "move".
>>>
>>>
>>> Am 07.01.2017 um 18:05 schrieb Raymond DeCampo:
>>>
>>> Is it possible to move existing JIRA issues from the commons-math project
>>>> to the commons-complex project or do we need to manually duplicate them
>>>> and
>>>> refer to the old ones?
>>>>
>>>>
>>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>
