You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Andrey Mashenkov <an...@gmail.com> on 2019/01/09 09:28:28 UTC
Re: [DISCUSSION] Relocation of Apache git repositories from
git-wip-us.apache.org to GitBox
Hi Dmitry,
Looks like repository has been transferred to GitBox,
but for now we still have incorrect links on wiki and ignite web site.
I've created a ticket [1]. Can someone fix this?
https://issues.apache.org/jira/browse/IGNITE-10863
On Sun, Dec 30, 2018 at 1:28 AM Dmitriy Pavlov <dp...@apache.org> wrote:
> Hi Igniters,
>
> Thanks to Peter and Alexey for sharing their opinion.
>
> I've filed https://issues.apache.org/jira/browse/INFRA-17516 to migrate.
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 13 дек. 2018 г. в 21:47, Peter Ivanov <pi...@gridgain.com>:
>
> > There will be no problem with TC, as we use GitHub as main VCS root,
> using
> > ASF only for release (which I will reconfigure during release builds
> > refactoring and optimisations for AI 2.8).
> >
> >
> > > On 11 Dec 2018, at 19:25, Alexey Goncharuk <alexey.goncharuk@gmail.com
> >
> > wrote:
> > >
> > > Given that there is no option to stay on the old repository and
> > mass-migration is scheduled for Feb, 7th, I think it is better to prepare
> > and move the repository before the date.
> > >
> > > As far as I understand, from developers standpoint we only need to
> > change the git remote entry. Petr, Sergey, can you asses what changes are
> > need to be done in order to support this migration for TC and release
> > procedure?
> > >
> > > вт, 11 дек. 2018 г. в 19:20, Dmitriy Pavlov <dpavlov@apache.org
> <mailto:
> > dpavlov@apache.org>>:
> > > 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.
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > сб, 8 дек. 2018 г. в 00:16, Dmitriy Pavlov <dpavlov@apache.org
> <mailto:
> > 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 <mailto:
> humbedooh@apache.org
> > >>
> > > > Date: пт, 7 дек. 2018 г. в 19:52
> > > > Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> > > > git-wip-us.apache.org <http://git-wip-us.apache.org/>
> > > > To: users@infra.apache.org <ma...@infra.apache.org> <
> > users@infra.apache.org <ma...@infra.apache.org>>
> > > >
> > > >
> > > > [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 <http://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 <http://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 <
> > 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 <mailto:
> > users@infra.apache.org>, not your
> > > > project's dev list :-).
> > > >
> > > >
> > > >
> >
> >
>
--
Best regards,
Andrey V. Mashenkov
Re: [DISCUSSION] Relocation of Apache git repositories from
git-wip-us.apache.org to GitBox
Posted by Dmitriy Pavlov <dp...@apache.org>.
Done for the wiki, we need update site.
ср, 9 янв. 2019 г. в 12:28, Andrey Mashenkov <an...@gmail.com>:
> Hi Dmitry,
>
> Looks like repository has been transferred to GitBox,
> but for now we still have incorrect links on wiki and ignite web site.
>
> I've created a ticket [1]. Can someone fix this?
>
> https://issues.apache.org/jira/browse/IGNITE-10863
>
> On Sun, Dec 30, 2018 at 1:28 AM Dmitriy Pavlov <dp...@apache.org> wrote:
>
>> Hi Igniters,
>>
>> Thanks to Peter and Alexey for sharing their opinion.
>>
>> I've filed https://issues.apache.org/jira/browse/INFRA-17516 to migrate.
>>
>> Sincerely,
>> Dmitriy Pavlov
>>
>> чт, 13 дек. 2018 г. в 21:47, Peter Ivanov <pi...@gridgain.com>:
>>
>> > There will be no problem with TC, as we use GitHub as main VCS root,
>> using
>> > ASF only for release (which I will reconfigure during release builds
>> > refactoring and optimisations for AI 2.8).
>> >
>> >
>> > > On 11 Dec 2018, at 19:25, Alexey Goncharuk <
>> alexey.goncharuk@gmail.com>
>> > wrote:
>> > >
>> > > Given that there is no option to stay on the old repository and
>> > mass-migration is scheduled for Feb, 7th, I think it is better to
>> prepare
>> > and move the repository before the date.
>> > >
>> > > As far as I understand, from developers standpoint we only need to
>> > change the git remote entry. Petr, Sergey, can you asses what changes
>> are
>> > need to be done in order to support this migration for TC and release
>> > procedure?
>> > >
>> > > вт, 11 дек. 2018 г. в 19:20, Dmitriy Pavlov <dpavlov@apache.org
>> <mailto:
>> > dpavlov@apache.org>>:
>> > > 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.
>> > >
>> > > Sincerely,
>> > > Dmitriy Pavlov
>> > >
>> > > сб, 8 дек. 2018 г. в 00:16, Dmitriy Pavlov <dpavlov@apache.org
>> <mailto:
>> > 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 <mailto:
>> humbedooh@apache.org
>> > >>
>> > > > Date: пт, 7 дек. 2018 г. в 19:52
>> > > > Subject: [NOTICE] Mandatory relocation of Apache git repositories on
>> > > > git-wip-us.apache.org <http://git-wip-us.apache.org/>
>> > > > To: users@infra.apache.org <ma...@infra.apache.org> <
>> > users@infra.apache.org <ma...@infra.apache.org>>
>> > > >
>> > > >
>> > > > [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 <http://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 <http://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 <
>> > 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 <mailto:
>> > users@infra.apache.org>, not your
>> > > > project's dev list :-).
>> > > >
>> > > >
>> > > >
>> >
>> >
>>
>
>
> --
> Best regards,
> Andrey V. Mashenkov
>