he.org
Cc: bui...@solr.apache.org
Subject: RE: Repository fork (master) about to happen (Wednesday)
Hi,
I already changed the Solr-Refguide and Solr-Artifact builds to use the
bui...@solr.apache.org <mailto:bui...@solr.apache.org> mailing list for build
mails. I also cleaned up some o
+1
-
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Dawid Weiss
> Sent: Wednesday, March 10, 2021 8:56 AM
> To: Lucene Dev
> Subject: Re: Repository fork (master) about to ha
> The question is whether branch_8x work would happen in lucene.git or in
> lucene-solr.git? Perhaps lucene-solr.git is most logical. Dawid?
If we want to keep the previous build infrastructure then I personally
think lucene-solr.git is most suitable. Main branches move to their
corresponding
what happens with the PR in Githubs user
>> >> interface.
>> >>
>> >> This question was asked many times, answer is simple: NO you can't move
>> >> over
>> >> Pull requests to different repositories on Github! It's also impossible
>
gt;>>> >
>>>>> > - Check pull requests and count how many affect solr and how many
>>>>> affect Lucene.
>>>>> > - In cooperation with Infra rename the Github project
>>>>> ("apache/lucene-solr.git") to "apache/luc
@thetaphi.de
From: Uwe Schindler
Sent: Tuesday, March 9, 2021 4:22 PM
To: dev@lucene.apache.org
Subject: RE: Repository fork (master) about to happen (Wednesday)
Hi Dawid,
give me a short ping when you start tomorrow. I will disable master jenkins
jobs possibly this evening.
Uwe
uesday, March 9, 2021 9:01 AM
To: Lucene Dev
Subject: Re: Repository fork (master) about to happen (Wednesday)
Yes, I can do this. I have meetings on Wednesday, but I can already do this
tomorrow evening.
I think we can live with this. Please disable those jenkins jobs at your
conve
> Yes, I can do this. I have meetings on Wednesday, but I can already do
> this tomorrow evening.
>
I think we can live with this. Please disable those jenkins jobs at your
convenience, thank you Uwe.
> Yes. Basically, we can duplicate the jobs and run the same command, just
> with different
> Can we provide a sequence of git commands for folks to run? Or will the
> official guidance be to create new local clones of each repo?
Yes, I will do that in the readme file placed on master branch, once cleaned up.
Don't panic, please. git is a wonderful version control system in that
it
> I am curious as to the status of /solr code being buildable without /lucene.
> The steps above at #2 say for each project to remove the other side. Is Solr
> ready? Where will Solr get the Lucene binaries?
https://issues.apache.org/jira/browse/SOLR-14759
peration with Apache Infra stuff, because we can'
> > change the Github repo settings or rename them using the Github UI.
> >
> > Uwe
> >
> > -
> > Uwe Schindler
> > Achterdiek 19, D-28357 Bremen
> > https://www.thetaphi.de <https://www.thetaphi
> - In cooperation with Infra rename the Github project
>>>> ("apache/lucene-solr.git") to "apache/lucene.git" (if more pull requests
>>>> affect Lucene) or "apache/solr.git" (if more are Solr). The PRs will
>>>> survive the rename. Al
gt; survive the rename. Also the old GitHub URL will redirect to the renamed
>>> one. The other project should be created as a fork - of course without PRs.
>>> >
>>> > We can only do this in cooperation with Apache Infra stuff, because we
>>> can' change the G
have to recreate them.
>> >>
>> >> Dawid is correct: You can merge the pull request also into another
>> rlocal
>> >> repository, but this is impossible with the Github UI. So basically,
>> you have to
>> >> read the email that comes
basically,
> you have to
> >> read the email that comes in with the Pull Request that lists the link
> to the
> >> branch and patch. Then use git command line (or Tortoise) and copypaste
> the
> >> URL there as "source branch" for the merge. Then yo
taphi.de
>
>> -Original Message-
>> From: Uwe Schindler
>> Sent: Monday, March 8, 2021 5:16 PM
>> To: dev@lucene.apache.org
>> Subject: RE: Repository fork (master) about to happen (Wednesday)
>>
>> I think the problem was what happens with
Hi Dawid,
> My plan is as follows:
>
> 1. DISABLE CI jobs and anything that pulls from current master. (Uwe,
> would you do help me with this?)
Yes, I can do this. I have meetings on Wednesday, but I can already do this
tomorrow evening.
> 2. Branch master to lucene/main and solr/main. Remove
the
> > URL there as "source branch" for the merge. Then you execute the merge,
> > squash and commit/push.
> >
> > Uwe
> >
> > -----
> > Uwe Schindler
> > Achterdiek 19, D-28357 Bremen
> > https://www.thetaphi.de
> > eM
; From: Uwe Schindler
> Sent: Monday, March 8, 2021 5:16 PM
> To: dev@lucene.apache.org
> Subject: RE: Repository fork (master) about to happen (Wednesday)
>
> I think the problem was what happens with the PR in Githubs user interface.
>
> This question was asked m
he merge. Then you execute
> the merge, squash and commit/push.
>
> Uwe
>
> -
> Uwe Schindler
> Achterdiek 19, D-28357 Bremen
> https://www.thetaphi.de
> eMail: u...@thetaphi.de
>
> > -Original Message-
> > From: Dawid Weiss
> > Sent: Mon
rch 8, 2021 3:25 PM
> To: Lucene Dev
> Subject: Re: Repository fork (master) about to happen (Wednesday)
>
> > What happens to open PRs?
>
> A pull request on github is essentially a diff between two commits.
> Existing PRs have to be placed on top of the new development branc
> What happens to open PRs?
A pull request on github is essentially a diff between two commits.
Existing PRs have to be placed on top of the new development branch.
Note these repositories are (initially) identical with lucene-solr so
if somebody clones the solr repo and the solr-lucene repo,
What happens to open PRs?
On Mon, 8 Mar 2021 at 7:28 PM, Dawid Weiss wrote:
> I think my message got buried among other messages, so starting a new
> thread.
>
> With Solr established, I think we're ready to proceed with forking the
> git repository from:
>
>
23 matches
Mail list logo
