We had the conversation at Slack channel. I asked you to propose the plan to mailing list, because ASF requires decisions are made in mailing list.
“ sounds good. we can merge the pull request and let both CI running for a while. once the Github Action shows the stability, we can cut over to the github actions. Can you propose the plan in mailing list? “ Sijie On Wed, Nov 20, 2019 at 4:00 PM Ali Ahmed <alahmed...@gmail.com> wrote: > Understood I will send out an email for a vote. > > My prior understanding was we had consensus on migration and we were > waiting for the service to go GA. > > > > On Wed, Nov 20, 2019 at 3:52 PM Sijie Guo <guosi...@gmail.com> wrote: > > > Hi Ali, > > > > To follow Apache way, you should raise a discussion or a vote for your > plan > > before giving out a notice like this. > > > > Every decision should be made via email thread, otherwise it never > happens. > > > > So please please follow the Apache way. > > > > Sijie > > > > On Wed, Nov 20, 2019 at 3:47 PM Ali Ahmed <alahmed...@gmail.com> wrote: > > > > > The github checkin for the ci process is ready, I have added caching > and > > > disabled runs for documentation changes. It will be merged soon but as > > non > > > required tasks for checkins so prs can still be merged without it > > passing. > > > > > > The goal is to check for stability for a few days and then file a > ticket > > > with apache infra to disable the current jenkins jobs soon after. > > > > > > https://github.com/apache/pulsar/pull/5642 > > > > > > Other pulsar sub projects should start there migration also. > > > > > >
