You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@reef.apache.org by Douglas Service <ds...@gmail.com> on 2016/09/30 20:37:02 UTC

Move REEF 335 to top level

I am planning on starting 'REEF-335 Remove the use of managed C++ in the
bridge' (a child of 334) as soon as I finish REEF-1624. However I think it
would be best to close 335 and then create a top level improvement that
links to back to 334 so I can break the work into a series of sub-tasks to
reduce risk since this is a fairly large change.

Comments? Suggestions?

Doug

Re: Move REEF 335 to top level

Posted by Douglas Service <ds...@gmail.com>.

Okay I will try to convert 335 to a top level improvement.

On Fri, Sep 30, 2016 at 9:32 PM, Markus Weimer <ma...@weimo.de> wrote:

> On 2016-09-30 1:37 PM, Douglas Service wrote:
>
>> I am planning on starting 'REEF-335 Remove the use of managed C++ in the
>> bridge' (a child of 334) as soon as I finish REEF-1624. However I think it
>> would be best to close 335 and then create a top level improvement that
>> links to back to 334 so I can break the work into a series of sub-tasks to
>> reduce risk since this is a fairly large change.
>>
>
> Sure. You can also convert [REEF-335] to a top-level item.
>
> Markus
>

Re: Move REEF 335 to top level

Posted by Markus Weimer <ma...@weimo.de>.

On 2016-09-30 1:37 PM, Douglas Service wrote:
> I am planning on starting 'REEF-335 Remove the use of managed C++ in the
> bridge' (a child of 334) as soon as I finish REEF-1624. However I think it
> would be best to close 335 and then create a top level improvement that
> links to back to 334 so I can break the work into a series of sub-tasks to
> reduce risk since this is a fairly large change.

Sure. You can also convert [REEF-335] to a top-level item.

Markus