I think we should cast a vote, isn't it?

Regards,
Tommaso

Il giorno mer 30 gen 2019 alle ore 09:27 Xue Junkai <j...@apache.org>
ha scritto:
>
> Thanks for the reminder. We are agree to move the gitbox.
>
> Best,
>
> Junkai
>
> On Wed, Jan 30, 2019 at 12:10 AM Apache Infrastructure Team 
> <infrastruct...@apache.org> wrote:
>>
>> Hello again, helix folks.
>> This is a reminder that you have *one week left* before the mandatory
>> mass-migration from git-wip-us to gitbox.
>>
>> As stated earlier in 2018, and reiterated a few times, all git
>> repositories must be migrated from the git-wip-us.apache.org URL to
>> gitbox.apache.org, as the old service is being decommissioned. Your
>> project is receiving this email because you still have repositories on
>> git-wip-us that needs to be migrated.
>>
>> The following repositories on git-wip-us belong to your project:
>>  - helix.git
>>
>>
>> We are now entering the remaining one week of the mandated
>> (coordinated) move stage of the roadmap, and you are asked to please
>> coordinate migration with the Apache Infrastructure Team before February
>> 7th. All repositories not migrated on February 7th will be mass migrated
>> without warning, and we'd appreciate it if we could work together to
>> avoid a big mess that day :-).
>>
>> As stated earlier, moving to gitbox means you will get full write access
>> on GitHub as well, and be able to close/merge pull requests and much
>> more. The move is mandatory for all Apache projects using git.
>>
>> To have your repositories moved, please follow these steps:
>>
>> - Ensure consensus on the move (a link to a lists.apache.org thread will
>>   suffice for us as evidence).
>> - Create a JIRA ticket at https://issues.apache.org/jira/browse/INFRA
>>
>> Your migration should only take a few minutes. If you wish to migrate
>> at a specific time of day or date, please do let us know in the ticket,
>> otherwise we will migrate at the earliest convenient time.
>>
>> There will be redirects in place from git-wip to gitbox, so requests
>> using the old remote origins should still work (however we encourage
>> people to update their remotes once migration has completed).
>>
>> As always, we appreciate your understanding and patience as we move
>> things around and work to provide better services and features for
>> the Apache Family.
>>
>> Should you wish to contact us with feedback or questions, please do so
>> at: us...@infra.apache.org.
>>
>>
>> With regards,
>> Apache Infrastructure
>>

Reply via email to