ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Pavlov <dpav...@apache.org>
Subject Re: [DISCUSSION] Relocation of Apache git repositories from git-wip-us.apache.org to GitBox
Date Tue, 11 Dec 2018 16:20:05 GMT
Hi All,

The Apache Ignite still has a repository on git-wip-us for its code, as
well, for release.

Does anyone have a problem with moving over the Ignite git-wip-us
repository to gitbox voluntarily? This means integrated access and easy PRs
(write access to the GitHub repo).

We need to document support for the decision from a mailing list post, so
here it is.

Dmitriy Pavlov

сб, 8 дек. 2018 г. в 00:16, Dmitriy Pavlov <dpavlov@apache.org>:

> Hi Igniters,
> What do you think about the voluntary migration of project repositories
> from git-wip to GitBox? (See details in the forwarded email.)
> Redirection of emails originated by PR actions to notifications@ seems to
> be almost finished, so email flood issue seems to be already solved for dev@
> .
> It is up to us to decide if we would like to migrate sooner. Later all
> repositories will be migrated anyway.
> Affected repositories
> - Ignite Release
> - Ignite
> Please share your opinion.
> Sincerely,
> Dmitriy Pavlov
> ---------- Forwarded message ---------
> From: Daniel Gruno <humbedooh@apache.org>
> Date: пт, 7 дек. 2018 г. в 19:52
> Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> git-wip-us.apache.org
> To: users@infra.apache.org <users@infra.apache.org>
> 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 users@infra.apache.org, not your
> project's dev list :-).

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message