Fwd: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Fwd: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org

Sean Owen-3
See below: Apache projects are migrating to a new git infrastructure,
and are seeking projects to volunteer to move earlier than later. I
believe Spark should volunteer.

This should mostly affect committers, who would need to point to the
new remote. It could affect downstream consumers of the Apache github
repo in the same way.

This change will let committers do things like close pull requests and
merge directly from the Github UI, if desired. We won't abandon our
merge script yet though, as it can do things like update JIRA and
cherry-picks for us.

It also opens up the possibility of using Github Issues instead of
JIRA, but that is something to consider for later.

Any concerns about volunteering for the move? (We'll have to eventually.)



---------- Forwarded message ---------
From: Daniel Gruno <[hidden email]>
Date: Fri, Dec 7, 2018 at 10:53 AM
Subject: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
To: [hidden email] <[hidden email]>


[IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE
  DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS]

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 gitbox.apache.org.

## 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
GitHub.

## 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)
   relocation
- 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 (gitbox.apache.org) OR GitHub for your development
and code pushes. To be able to use GitHub, please follow the primer
at: https://reference.apache.org/committer/github


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
well.

With regards, Daniel on behalf of ASF Infra.

PS:For inquiries, please reply to [hidden email], not your
project's dev list :-).



---------------------------------------------------------------------
To unsubscribe e-mail: [hidden email]

---------------------------------------------------------------------
To unsubscribe e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org

shane knapp
no concerns, and this sounds great to me!

On Fri, Dec 7, 2018 at 12:41 PM Sean Owen <[hidden email]> wrote:
See below: Apache projects are migrating to a new git infrastructure,
and are seeking projects to volunteer to move earlier than later. I
believe Spark should volunteer.

This should mostly affect committers, who would need to point to the
new remote. It could affect downstream consumers of the Apache github
repo in the same way.

This change will let committers do things like close pull requests and
merge directly from the Github UI, if desired. We won't abandon our
merge script yet though, as it can do things like update JIRA and
cherry-picks for us.

It also opens up the possibility of using Github Issues instead of
JIRA, but that is something to consider for later.

Any concerns about volunteering for the move? (We'll have to eventually.)



---------- Forwarded message ---------
From: Daniel Gruno <[hidden email]>
Date: Fri, Dec 7, 2018 at 10:53 AM
Subject: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
To: [hidden email] <[hidden email]>


[IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE
  DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS]

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 gitbox.apache.org.

## 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
GitHub.

## 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)
   relocation
- 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 (gitbox.apache.org) OR GitHub for your development
and code pushes. To be able to use GitHub, please follow the primer
at: https://reference.apache.org/committer/github


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
well.

With regards, Daniel on behalf of ASF Infra.

PS:For inquiries, please reply to [hidden email], not your
project's dev list :-).



---------------------------------------------------------------------
To unsubscribe e-mail: [hidden email]

---------------------------------------------------------------------
To unsubscribe e-mail: [hidden email]



--
Shane Knapp
UC Berkeley EECS Research / RISELab Staff Technical Lead
Reply | Threaded
Open this post in threaded view
|

Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org

Dongjoon Hyun-2
+1 for moving to new git infra.

Bests,
Dongjoon.

On Fri, Dec 7, 2018 at 12:53 PM shane knapp <[hidden email]> wrote:
no concerns, and this sounds great to me!

On Fri, Dec 7, 2018 at 12:41 PM Sean Owen <[hidden email]> wrote:
See below: Apache projects are migrating to a new git infrastructure,
and are seeking projects to volunteer to move earlier than later. I
believe Spark should volunteer.

This should mostly affect committers, who would need to point to the
new remote. It could affect downstream consumers of the Apache github
repo in the same way.

This change will let committers do things like close pull requests and
merge directly from the Github UI, if desired. We won't abandon our
merge script yet though, as it can do things like update JIRA and
cherry-picks for us.

It also opens up the possibility of using Github Issues instead of
JIRA, but that is something to consider for later.

Any concerns about volunteering for the move? (We'll have to eventually.)



---------- Forwarded message ---------
From: Daniel Gruno <[hidden email]>
Date: Fri, Dec 7, 2018 at 10:53 AM
Subject: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
To: [hidden email] <[hidden email]>


[IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE
  DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS]

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 gitbox.apache.org.

## 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
GitHub.

## 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)
   relocation
- 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 (gitbox.apache.org) OR GitHub for your development
and code pushes. To be able to use GitHub, please follow the primer
at: https://reference.apache.org/committer/github


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
well.

With regards, Daniel on behalf of ASF Infra.

PS:For inquiries, please reply to [hidden email], not your
project's dev list :-).



---------------------------------------------------------------------
To unsubscribe e-mail: [hidden email]

---------------------------------------------------------------------
To unsubscribe e-mail: [hidden email]



--
Shane Knapp
UC Berkeley EECS Research / RISELab Staff Technical Lead