+1 (binding) for the move as well. @Jake Maes <jm...@linkedin.com> I think our merge script requires setting up a local alias 'apache-samza' for the remote repo. Hence, it should be a simple step to point the 'apache-samza' repo to the new repo on gitbox, hopefully.
-Yi On Tue, Jan 15, 2019 at 12:12 PM Jake Maes <jma...@apache.org> wrote: > Yeah, sounds pretty light weight. > > Quick question for committers: Do we anticipate this affecting our merge > script? Perhaps we won't need the merge script, since we'll be able to use > github directly. Thoughts? > > -Jake > > On Tue, Jan 15, 2019 at 11:49 AM Prateek Maheshwari <prateek...@gmail.com> > wrote: > > > Thanks for starting the discussion Pawas. I'm +1 (binding) for the > > migration. > > > > - Prateek > > > > On Tue, Jan 15, 2019 at 11:44 AM Pawas Chhokra <pawas2...@gmail.com> > > wrote: > > > > > > Hi all, > > > > > > As mandated by the Apache Infrastructure Team, all git repositories > must > > be > > > migrated from git-wip-us.apache.org URL to gitbox.apache.org, as the > old > > > service is being decommissioned. This needs to happen before February > > 7th, > > > and this ticket <https://issues.apache.org/jira/browse/SAMZA-2060> is > to > > > check if migrating Samza on 11 AM, Jan 25, 2019 is acceptable to > > everyone. > > > > > > Thanks & Regards, > > > Pawas Chhokra > > >
