Thanks for starting the discussion Kevin, Sorry for jumping in late, I think we should move proactively so we have time to iron out issues with the migration, if any, so here's my +1
Best, Sandeep On Mon, Dec 10, 2018 at 9:32 AM Kevin Risden <[email protected]> wrote: > The below line is from the notice. Maybe a VOTE isn't necessary, but > doesn't hurt :) > > - Consensus in the project (documented via the mailing list) > > Kevin Risden > > > On Mon, Dec 10, 2018 at 5:28 AM Colm O hEigeartaigh <[email protected]> > wrote: > > > I'm not sure it's necessary to have a vote - it should be fine if the PMC > > chair files the JIRA with INFRA. > > > > Colm. > > > > On Fri, Dec 7, 2018 at 6:46 PM > > Kevin Risden > > <[email protected]> wrote: > > > > > So I knew this was coming and just hadn't gotten around to sending an > > email > > > out about moving from git-wip to gitbox. For reference see email > subject > > > "[NOTICE] Mandatory relocation of Apache git repositories on > > > git-wip-us.apache.org" > > > > > > I think there are some benefits to moving before we are forced to in > > 2019. > > > For the most part this will likely require updating remotes in local > git > > > checkouts. There are a few references to git-wip in our developer > > > documentation that needs to be updated as well. > > > > > > If there is interest in moving before being forced, I can start a VOTE > > > thread which we can then use to have INFRA move from git-wip to gitbox. > > > > > > I suggest we move after the 1.2.0 release and not during ;) > > > > > > Kevin Risden > > > > > > > > > -- > > Colm O hEigeartaigh > > > > Talend Community Coder > > http://coders.talend.com > > >
