osdir.com


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

Re: Brooklyn git -- git-wip-us GONE now gitbox or github


I kept the Gitbox remote just in case. But I agree with you Geoff, we don't
need another remote anymore.

On Fri, 14 Dec 2018 at 22:57 Geoff Macartney <geoff.macartney@xxxxxxxxx>
wrote:

> Do we even need to have a remote for git-wip-us any more? Now that we can
> merge on Github I've removed the repo I had for merging PRs altogether!
>
>
>
>
>
> On Fri, 14 Dec 2018 at 12:28 Alex Heneveld <
> alex.heneveld@xxxxxxxxxxxxxxxxx>
> wrote:
>
> >
> > As per thread below:  my `git pull` just failed, but this command in the
> > root brooklyn dir worked seamlessly for me:
> >
> > *    for x in .git/{config,modules/*/config} ; do sed -i.bk
> > s/git-wip-us/gitbox/g $x ; done**
> > *
> > (I use submodules; slight tweaks should take care of it for other
> > topologies.)
> >
> > Best
> > Alex
> >
> >
> > On 14/12/2018 10:52, Thomas Bouron wrote:
> > > Erratum: we now have a team for the people who did the Gitbox <->
> GitHub
> > > link, which gives committers the ability to merge PR directly from the
> > > GitHub UI 🎉
> > >
> > >
> > > On Fri, 14 Dec 2018 at 10:18 Thomas Bouron <thomas.bouron@xxxxxxxxxxxx
> >
> > > wrote:
> > >
> > >> Migration successful[1]. It means that committers can push to either
> > >> Gitbox or GitHub (still cannot merge directly through the UI though)
> > >>
> > >> [1]
> > >>
> >
> https://issues.apache.org/jira/browse/INFRA-17440?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
> > >>
> > >> On Fri, 14 Dec 2018 at 08:44 Thomas Bouron <
> thomas.bouron@xxxxxxxxxxxx>
> > >> wrote:
> > >>
> > >>> Hi all.
> > >>>
> > >>> I think we have reached a consensus here as there is no +0 or -1.
> > >>> I went ahead and created an INFRA ticket[1] to request the move.
> > >>>
> > >>> Best.
> > >>>
> > >>> [1] https://issues.apache.org/jira/browse/INFRA-17440
> > >>>
> > >>> On Thu, 13 Dec 2018 at 13:53 John Campbell <
> > >>> john.campbell@xxxxxxxxxxxxxxxxx> wrote:
> > >>>
> > >>>> No strong feelings, so +1 from me
> > >>>>
> > >>>> John Campbell
> > >>>> Software Engineer
> > >>>>
> > >>>> Cloudsoft | Bringing Business to the Cloud
> > >>>>
> > >>>> E: John.campbell@xxxxxxxxxxxxxxxxx
> > >>>> M: 07779 576614
> > >>>> T: -
> > >>>> L: www.linkedin.com/in/john-campbell-42105267
> > >>>>
> > >>>> Need a hand with AWS? Get a Free Consultation.
> > >>>>
> > >>>>> On 13 Dec 2018, at 09:31, Duncan Grant <duncan.grant@xxxxxxxxxxxx>
> > >>>> wrote:
> > >>>>> +1
> > >>>>>
> > >>>>> On Wed, 12 Dec 2018 at 16:42 Richard Downer <richard@xxxxxxxxxx>
> > >>>> wrote:
> > >>>>>> Brooklyn team,
> > >>>>>>
> > >>>>>> Apart from myself, I don't think anyone has clearly come out in
> > >>>> favour or
> > >>>>>> opposed to this. I'd rather we got consensus and moved to gitbox
> > >>>> early - so
> > >>>>>> that if some people do object, we have time to work out the
> > >>>> objections with
> > >>>>>> infra, before we are involuntarily moved.
> > >>>>>>
> > >>>>>> Thoughts, anyone? Does this need a formal vote to get people
> > >>>> responding?
> > >>>>>> Richard.
> > >>>>>>
> > >>>>>>
> > >>>>>> On Fri, 7 Dec 2018 at 16:54, Daniel Gruno <humbedooh@xxxxxxxxxx>
> > >>>> wrote:
> > >>>>>>> [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 :-).
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>> --
> > >>>>> Duncan Grant
> > >>>>> Software Engineer
> > >>>>>
> > >>>>> *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the
> Cloud
> > >>>>>
> > >>>>> Need a hand with AWS? Get a Free Consultation.
> > >>>>> <https://go.cloudsoft.io/healthcheck/>
> > >>>> --
> > >>> Thomas Bouron
> > >>> Senior Software Engineer
> > >>>
> > >>> *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
> > >>>
> > >>> GitHub: https://github.com/tbouron
> > >>> Twitter: https://twitter.com/eltibouron
> > >>>
> > >>> Need a hand with AWS? Get a Free Consultation.
> > >>>
> > >> --
> > >> Thomas Bouron
> > >> Senior Software Engineer
> > >>
> > >> *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
> > >>
> > >> GitHub: https://github.com/tbouron
> > >> Twitter: https://twitter.com/eltibouron
> > >>
> > >> Need a hand with AWS? Get a Free Consultation.
> > >>
> >
> >
>
-- 
Thomas Bouron
Senior Software Engineer

*Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud

GitHub: https://github.com/tbouron
Twitter: https://twitter.com/eltibouron

Need a hand with AWS? Get a Free Consultation.