osdir.com


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

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


Sorry for the silence on this.

Julian, I'd like to deploy the site, but when I build, I see the latest
release announcement disappear. Given your reminder that site and master
should be the same after a release, I'll try to sort through what's going
on later today.

On Thu, Dec 27, 2018, 16:04 Julian Hyde <jhyde@xxxxxxxxxx wrote:

> Thanks, Francis.
>
> $ git remote set-url origin
> https://gitbox.apache.org/repos/asf/calcite.git <
> https://gitbox.apache.org/repos/asf/calcite.git>
>
> was sufficient to allow me to pull/fetch. And after I linked accounts
> using https://gitbox.apache.org/ <https://gitbox.apache.org/> I was able
> to also push.
>
> The “site” branch is now in sync with “master”, which is as it should be,
> right after a release.
>
> Michael, Did you know that your commit
> https://github.com/apache/calcite/commit/9d50e6d7418579c5a73d872e6aec5924ed97c239
> <
> https://github.com/apache/calcite/commit/9d50e6d7418579c5a73d872e6aec5924ed97c239>
> is in git but is not deployed to the site (via svn)? I’ll let you publish
> when you are ready.
>
> Julian
>
>
> > On Dec 25, 2018, at 11:46 PM, Francis Chuang <francischuang@xxxxxxxxxx>
> wrote:
> >
> > I haven't tried pushing directly to Github yet, but did you link your
> Github and Apache accounts here: https://gitbox.apache.org/ ?
> >
> > On 26/12/2018 6:35 pm, Julian Hyde wrote:
> >> Regarding the “site” branch. After a release, it should always point to
> the same as “master”. (It may diverge later, if there are changes made to
> the web site in master branch that we do not wish to immediately publish.)
> Sorry I forgot to push to site.
> >>
> >> Regarding gitbox. How should I set up my environment? I previously had
> origin as follows:
> >>
> >> $ git remote -v |grep origin
> >> origin       https://git-wip-us.apache.org/repos/asf/calcite.git
> (fetch)
> >> origin       https://git-wip-us.apache.org/repos/asf/calcite.git (push)
> >>
> >> Now I point it to GitHub, as follows:
> >>
> >> $ git remote set-url origin git@xxxxxxxxxx:apache/calcite.git
> >>
> >> but I am not able to push.
> >>
> >> Julian
> >>
> >>
> >>> On Dec 25, 2018, at 7:56 PM, Andrei Sereda <andrei@xxxxxxxxx> wrote:
> >>>
> >>> Just in case.
> >>>
> >>> I made some changes to elastic adapter documentation (but didn't deploy
> >>> them)  :
> >>> 1) c3e076c0
> >>> <
> https://github.com/apache/calcite/commit/c3e076c0b8bc3b4f69d90cf08f7c6a082a4fe564
> >
> >>>
> >>> 2) af739cbe
> >>> <
> https://github.com/apache/calcite/commit/af739cbef3799512d095134567ca715b1179611a
> >
> >>>
> >>> My changes should be in both master and site branches.
> >>>
> >>> On Tue, Dec 25, 2018 at 9:48 PM Francis Chuang <
> francischuang@xxxxxxxxxx>
> >>> wrote:
> >>>
> >>>> When I deployed the changes to update the PMC Chair, I deployed the
> >>>> master branch. I checked out the site branch, but it appeared to be
> >>>> missing the site commits for Calcite 1.18 release and since I don't
> >>>> commit to Calcite often, I didn't want to cherry-pick the commits into
> >>>> the site branch and potentially break things.
> >>>>
> >>>> I think deploying the master branch should be safe for now, because
> 1.18
> >>>> was just released and there hasn't been any changes to the site for
> 1.19
> >>>> yet.
> >>>>
> >>>> On 26/12/2018 1:02 pm, Michael Mior wrote:
> >>>>> I've made commits to master to update the site but somehow my site
> branch
> >>>>> seems to be out of sync with what's deployed. If someone who has
> deployed
> >>>>> the site recently has a chance to check it out that would be great.
> >>>>>
> >>>>> --
> >>>>> Michael Mior
> >>>>> mmior@xxxxxxxxxx
> >>>>>
> >>>>>
> >>>>> Le mar. 25 déc. 2018 à 16:20, Michael Mior <michael.mior@xxxxxxxxx>
> a
> >>>>> écrit :
> >>>>>
> >>>>>> The migration is already done to my surprise. I'll try to update the
> >>>> site
> >>>>>> and send out an announcement to committers later today.
> >>>>>>
> >>>>>> On Tue, Dec 25, 2018, 16:15 Francis Chuang <
> francischuang@xxxxxxxxxx
> >>>>>> wrote:
> >>>>>>
> >>>>>>> Thanks for sorting this out, Michael! Can't wait to try it!
> >>>>>>>
> >>>>>>> On 26/12/2018 2:13 am, Michael Mior wrote:
> >>>>>>>> Since there have been no objections and the release is now
> complete,
> >>>>>>> I've
> >>>>>>>> requested the migration.
> >>>>>>>>
> >>>>>>>> https://issues.apache.org/jira/browse/INFRA-17498
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> Michael Mior
> >>>>>>>> mmior@xxxxxxxxxx
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Le ven. 7 déc. 2018 à 11:54, Daniel Gruno <humbedooh@xxxxxxxxxx>
> a
> >>>>>>> écrit :
> >>>>>>>>> [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 users@xxxxxxxxxxxxxxxx, not
> your
> >>>>>>>>> project's dev list :-).
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>
> >
>
>