MesaTEE main repo transfer

[Yu Ding <di...@apache.org>]

Hey folks,

Are we ready to create a INFRA ticket for transferring MesaTEE main repo?

After the transfer is complete, how would the webhooks be like? The hooks
now is connected to our custom drone CI service ci.mesalock-linux.com. The
CI system seems need to grant "apache" to access its service. Should we
grant it during the transfer process, or after the transfer is done?

Best,
Yu

Re: MesaTEE main repo transfer

[Mingshen Sun <ms...@apache.org>]

Hi, the mesatee main repo has been transferred to
https://github.com/apache/incubator-mesatee.

The next step is to setup our previous infras (CI, code coverage,
review/merge rules, etc).

On Mon, Nov 4, 2019 at 1:23 PM Yu Ding <di...@gmail.com> wrote:

> JIRA issue created
>
> https://issues.apache.org/jira/browse/INFRA-19381
>
> Best,
> Yu
>
> On Sun, Nov 3, 2019 at 10:48 AM Yu Ding <di...@apache.org> wrote:
>
> > Hey folks,
> >
> > Are we ready to create a INFRA ticket for transferring MesaTEE main repo?
> >
> > After the transfer is complete, how would the webhooks be like? The hooks
> > now is connected to our custom drone CI service ci.mesalock-linux.com.
> > The CI system seems need to grant "apache" to access its service. Should
> we
> > grant it during the transfer process, or after the transfer is done?
> >
> > Best,
> > Yu
> >
>

Re: MesaTEE main repo transfer

[Yu Ding <di...@gmail.com>]

JIRA issue created

https://issues.apache.org/jira/browse/INFRA-19381

Best,
Yu

On Sun, Nov 3, 2019 at 10:48 AM Yu Ding <di...@apache.org> wrote:

> Hey folks,
>
> Are we ready to create a INFRA ticket for transferring MesaTEE main repo?
>
> After the transfer is complete, how would the webhooks be like? The hooks
> now is connected to our custom drone CI service ci.mesalock-linux.com.
> The CI system seems need to grant "apache" to access its service. Should we
> grant it during the transfer process, or after the transfer is done?
>
> Best,
> Yu
>