This was done yesterday, but it appears that our Jenkins jobs need to be updated? I looked at a couple of Ref Guide builds and doc changes I made yesterday and today aren’t showing up, but it’s hard for me to tell when looking at the other jobs for artifacts to know if that’s true for all the jobs or not.
Could someone who knows these jobs check? I think we have some wiki docs that need to be updated with the new repo address. I’ll get to it eventually unless someone has time sooner. Thanks, Cassandra On Jan 3, 2019, 10:23 AM -0600, David Smiley <david.w.smi...@gmail.com>, wrote: > https://issues.apache.org/jira/browse/INFRA-17534 > Good questions Erick; please post as a comment to the issue. > > > On Thu, Jan 3, 2019 at 11:21 AM Erick Erickson <erickerick...@gmail.com> > > wrote: > > > +1 and thanks! > > > > > > Any time works for me. I assume we'll get some idea of when it'll > > > happen, I'm also assuming that the git-wip-us.apache.org will just > > > completely stop working so there's no chance of pushing something to > > > the wrong place? > > > > > > > > > On Thu, Jan 3, 2019 at 8:15 AM David Smiley <david.w.smi...@gmail.com> > > > wrote: > > > > > > > > I agree with Uwe's sentiment. Essentially anywhere in your git remote > > > > configuration that refers to git-wip-us.apache.org will need to change > > > > to gitbox.apache.org open up .git/config to see what I mean. At your > > > > prerogative, you may instead work with GitHub's mirror exclusively -- a > > > > new option. If you want to do that, see https://gitbox.apache.org > > > > which is pretty helpful (do read it no matter what you do), and > > > > includes a link to the "account linking page". Personally, I intend to > > > > commit to gitbox but I will also link my accounts as I suspect this > > > > will enable more direct use of the GitHub website like closing old pull > > > > requests (unconfirmed). > > > > > > > > On Thu, Jan 3, 2019 at 10:57 AM Alan Woodward <romseyg...@gmail.com> > > > > wrote: > > > >> > > > >> +1, thanks for volunteering David! > > > >> > > > >> > > > >> On 3 Jan 2019, at 15:41, Jan Høydahl <jan....@cominvent.com> wrote: > > > >> > > > >> +1 > > > >> > > > >> -- > > > >> Jan Høydahl, search solution architect > > > >> Cominvent AS - www.cominvent.com > > > >> > > > >> 3. jan. 2019 kl. 14:45 skrev David Smiley <david.w.smi...@gmail.com>: > > > >> > > > >> I propose we (me) coordinate with them to do this transition on > > > >> Wednesday next week (Jan 9th). It appears to be a minor > > > >> inconvenience. If there are problems, we'll have some work days after > > > >> to deal with it. And doing this ahead of the mass migration may give > > > >> us more individual attention from the busy infra team if there are > > > >> problems. Can I get some +1's? > > > >> > > > >> On Thu, Jan 3, 2019 at 8:18 AM Apache Infrastructure Team > > > >> <infrastruct...@apache.org> wrote: > > > >>> > > > >>> Hello, lucene folks. > > > >>> As stated earlier in 2018, all git repositories must be migrated from > > > >>> the git-wip-us.apache.org URL to gitbox.apache.org, as the old service > > > >>> is being decommissioned. Your project is receiving this email because > > > >>> you still have repositories on git-wip-us that needs to be migrated. > > > >>> > > > >>> The following repositories on git-wip-us belong to your project: > > > >>> - lucene-solr.git > > > >>> > > > >>> > > > >>> We are now entering the mandated (coordinated) move stage of the > > > >>> roadmap, > > > >>> and you are asked to please coordinate migration with the Apache > > > >>> Infrastructure Team before February 7th. All repositories not migrated > > > >>> on February 7th will be mass migrated without warning, and we'd > > > >>> appreciate > > > >>> it if we could work together to avoid a big mess that day :-). > > > >>> > > > >>> Moving to gitbox means you will get full write access on GitHub as > > > >>> well, > > > >>> and be able to close/merge pull requests and much more. > > > >>> > > > >>> To have your repositories moved, please follow these steps: > > > >>> > > > >>> - Ensure consensus on the move (a link to a lists.apache.org thread > > > >>> will > > > >>> suffice for us as evidence). > > > >>> - Create a JIRA ticket at https://issues.apache.org/jira/browse/INFRA > > > >>> > > > >>> Your migration should only take a few minutes. If you wish to migrate > > > >>> at a specific time of day or date, please do let us know in the > > > >>> ticket. > > > >>> > > > >>> As always, we appreciate your understanding and patience as we move > > > >>> things around and work to provide better services and features for > > > >>> the Apache Family. > > > >>> > > > >>> Should you wish to contact us with feedback or questions, please do so > > > >>> at: us...@infra.apache.org. > > > >>> > > > >>> > > > >>> With regards, > > > >>> Apache Infrastructure > > > >>> > > > >>> > > > >>> --------------------------------------------------------------------- > > > >>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > > > >>> For additional commands, e-mail: dev-h...@lucene.apache.org > > > >>> > > > >> -- > > > >> Lucene/Solr Search Committer (PMC), Developer, Author, Speaker > > > >> LinkedIn: http://linkedin.com/in/davidwsmiley | Book: > > > >> http://www.solrenterprisesearchserver.com > > > >> > > > >> > > > >> > > > > -- > > > > Lucene/Solr Search Committer (PMC), Developer, Author, Speaker > > > > LinkedIn: http://linkedin.com/in/davidwsmiley | Book: > > > > http://www.solrenterprisesearchserver.com > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > > > For additional commands, e-mail: dev-h...@lucene.apache.org > > > > -- > Lucene/Solr Search Committer (PMC), Developer, Author, Speaker > LinkedIn: http://linkedin.com/in/davidwsmiley | Book: > http://www.solrenterprisesearchserver.com
