[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [NOTICE] Mandatory relocation of Apache git repositories on

I am also +1 on early move.

On 8/12/2018 5:51 am, Julian Hyde wrote:
+1 on early move

It should be low-impact; probably only committers are using <> anyway, everyone else is using

On Dec 7, 2018, at 10:41 AM, Kevin Risden <krisden@xxxxxxxxxx> wrote:

I'm +1 in moving before being forced to. I know a few other projects have
moved and didn't seem to cause too much harm. Would be good to do between
releases :)

Kevin Risden

On Fri, Dec 7, 2018 at 1:36 PM Michael Mior <mmior@xxxxxxxxxx> wrote:

Hi all,

We have a decision to make regarding repository hosting. INFRA is retiring which Calcite is currently using. We're going to
to move at some point in the next few months to The
question is whether we volunteer to do so relatively soon before we'll be
required to move. (More details in the message below.) My vote would be to
volunteer and get the move over with once the latest release is complete.
This move will have the nice advantage that we'll have write access to
GitHub directly.

Anyway, I'd suggest we come to a decision on our strategy relatively soon
so we can start thinking about what might need to change and when. Thanks!

Michael Mior

---------- Forwarded message ---------
From: Daniel Gruno <humbedooh@xxxxxxxxxx>
Date: ven. 7 déc. 2018 à 11:54
Subject: [NOTICE] Mandatory relocation of Apache git repositories on
To: users@xxxxxxxxxxxxxxxx <users@xxxxxxxxxxxxxxxx>


Hello Apache projects,

I am writing to you because you may have git repositories on the
git-wip-us server, which is slated to be decommissioned in the coming
months. All repositories will be moved to the new gitbox service which
includes direct write access on github as well as the standard ASF
commit access via

## Why this move? ##
The move comes as a result of retiring the git-wip service, as the
hardware it runs on is longing for retirement. In lieu of this, we
have decided to consolidate the two services (git-wip and gitbox), to
ease the management of our repository systems and future-proof the
underlying hardware. The move is fully automated, and ideally, nothing
will change in your workflow other than added features and access to

## Timeframe for relocation ##
Initially, we are asking that projects voluntarily request to move
their repositories to gitbox, hence this email. The voluntary
timeframe is between now and January 9th 2019, during which projects
are free to either move over to gitbox or stay put on git-wip. After
this phase, we will be requiring the remaining projects to move within
one month, after which we will move the remaining projects over.

To have your project moved in this initial phase, you will need:

- Consensus in the project (documented via the mailing list)
- File a JIRA ticket with INFRA to voluntarily move your project repos
   over to gitbox (as stated, this is highly automated and will take
   between a minute and an hour, depending on the size and number of
   your repositories)

To sum up the preliminary timeline;

- December 9th 2018 -> January 9th 2019: Voluntary (coordinated)
- January 9th -> February 6th: Mandated (coordinated) relocation
- February 7th: All remaining repositories are mass migrated.

This timeline may change to accommodate various scenarios.

## Using GitHub with ASF repositories ##
When your project has moved, you are free to use either the ASF
repository system ( OR GitHub for your development
and code pushes. To be able to use GitHub, please follow the primer

We appreciate your understanding of this issue, and hope that your
project can coordinate voluntarily moving your repositories in a
timely manner.

All settings, such as commit mail targets, issue linking, PR
notification schemes etc will automatically be migrated to gitbox as

With regards, Daniel on behalf of ASF Infra.

PS:For inquiries, please reply to users@xxxxxxxxxxxxxxxx, not your
project's dev list :-).