[almighty] Closing duplicate user-stories in almighty-core

[Konrad Kleine]

Hi Xavier,

I fully agree with closing the issues in almighty-core that have no further
comment after the migration happened.

Thank you for bringing this up!

Konrad

On Wed, Feb 1, 2017 at 10:50 AM, Xavier Coulon <xcoulon at redhat.com> wrote:

> Mickael et al.,
>
> There are user-stories that have been moved to the fabric8-planner repo
> without being closed in the almighty-core repository: https://github.
> com/almighty/almighty-core/issues?utf8=%E2%9C%93&q=is%
> 3Aopen%20label%3Auserstory%20%22This%20issue%20was%20moved%
> 20to%20fabric8io%2Ffabric8-planner%22%20
>
> I would suggest that every user-story in almighty-core that have no
> further comment after they have been moved (ie, after Mickael's comment
> such as https://github.com/almighty/almighty-core/issues/
> 638#issuecomment-271275690) be closed, along with a comment to suggest
> continuing the discussion on the related user-story in the fabric8-planner
> repo.
> However, user-stories such as https://github.com/almighty/
> almighty-core/issues/639 should remain open for now, since the discussion
> continued after the duplication.
>
> In any case, there might be some work needed in the almighty-core
> repository in order to complete user-stories of fabric8-planner, in which
> case new issues will be opened in almighty-core.
>
> What do you think about this proposal ?
>
> --
> Best regards,
> /Xavier
>
> _______________________________________________
> almighty-public mailing list
> almighty-public at redhat.com
> https://www.redhat.com/mailman/listinfo/almighty-public
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/almighty-public/attachments/20170201/a00c79c5/attachment.htm>