[
https://issues.apache.org/jira/browse/MYRIAD-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14908846#comment-14908846
]
Adam B commented on MYRIAD-143:
-------------------------------
For new changes, we can use PRs on the Apache github mirror:
https://github.com/apache/incubator-myriad/pulls
For existing PRs, we could review them on the old github and then apply the
patches manually to Apache git, or try to migrate the PRs over to the Apache
github mirror.
In Mesos, we use
https://github.com/apache/mesos/blob/master/support/apply-review.sh to apply RB
patches or github PRs.
> Migrate Myriad code-base to Apache git
> --------------------------------------
>
> Key: MYRIAD-143
> URL: https://issues.apache.org/jira/browse/MYRIAD-143
> Project: Myriad
> Issue Type: Improvement
> Reporter: Mohit Soni
> Assignee: Mohit Soni
>
> The code migration would entail following:
> * Mirroring https://github.com/mesos/myriad to Apache git:
> {quote}
> git clone --bare g...@github.com:mesos/myriad.git
> git push --mirror git://git.apache.org/incubator-myriad.git
> {quote}
> * Send email to dev-list confirming completion of code-migration.
> Post initial migration we'll continue sync Apache Git from
> https://github.com/mesos/myriad, until all the outstanding PRs are merged.
> Doing this will ensure that any current development activity happening on
> https://github.com/mesos/myriad is not disrupted.
> Once all outstanding PRs are merged, shutdown
> https://github.com/mesos/myriad, and migrate all new development work to
> Apache git repo.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
