Good idea. Assuming there are no objections on this thread, I'll ask the
infra people to plan it for a specific time at least a few days out and
then announce that time to this list

On Thu, Jan 3, 2019 at 9:44 AM Tim Armstrong <[email protected]>
wrote:

> It would be good to give everyone at least a few days to plan their
> migration and do it at a specific time for the convenience of others that
> might have jobs or infrastructure using git-wip-us.apache.org
>
> On Thu, Jan 3, 2019 at 9:26 AM Jim Apple <[email protected]> wrote:
>
> > And some jenkins.impala.io jobs
> >
> > On Thu, Jan 3, 2019 at 9:25 AM Joe McDonnell <[email protected]>
> > wrote:
> >
> > > +1 to going ahead with the migration
> > >
> > > bin/push_to_asf.py and bin/bootstrap_system.sh require updates when we
> > make
> > > the migration.
> > >
> > > -Joe
> > >
> > > On Thu, Jan 3, 2019 at 8:51 AM Jim Apple <[email protected]> wrote:
> > >
> > > > +1 to moving ahead of the mass migration.
> > > >
> > > > Any thoughts on this? I can do the paperwork.
> > > >
> > > >
> > > >
> > > > On Thu, Jan 3, 2019 at 5:19 AM Apache Infrastructure Team <
> > > > [email protected]> wrote:
> > > >
> > > > > Hello, impala folks.
> > > > > As stated earlier in 2018, 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:
> > > > >  - impala.git
> > > > >
> > > > >
> > > > > We are now entering 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 :-).
> > > > >
> > > > > 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.
> > > > >
> > > > > 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.
> > > > >
> > > > > 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: [email protected].
> > > > >
> > > > >
> > > > > With regards,
> > > > > Apache Infrastructure
> > > > >
> > > > >
> > > >
> > >
> >
>

Reply via email to