Re: Branch cleaning/ archiving

[Jan Høydahl]

I thought a simple git fetch would detect deleted branches?
Probably wise to send a mail to separate mail to dev@

-
Subject: [NOTICE] All branches will be gone on Monday

We plan to remove up all historic branches in the new solr.git repostiory, and 
leave
only the "main" branch. We'll do this by replacing the branch with a git tag, 
e.g.
branch_8x will be replaced with tag history/branches/lucene-solr/branch_8x.
This is the same procedure we did when moving from svn to git. No history is 
lost!

We encourage all committers to work on features in feature branches in your
private git fork instead of pushing your branches to the central repository.
For larger collaborative efforts like reference_branch and refactorings, it's ok
to use central branches.

Should you have a work-in-progress on a central feature branch, such as an
active PR against lucene-solr.git, please push the PR branch to your private
fork and re-create the PR in new repo using the private branch. All PRs will
need to be re-created anyway so this is a small extra step.

If you are aware of branches that should stay central, other than 
reference_impl_dev and reference_impl, please reply to this email.

The removal of these branches will happen on Monday March 15th.
After the removal you will need to run "git remote prune origin"

PS: The lucene-solr.git repo, where 8.x development continues, will not be 
affected.

-

> 11. mar. 2021 kl. 07:47 skrev Dawid Weiss :
> 
> This will also require people who already made their clones/ forks to
> prune their copy of the remote as this isn't done automatically.
> 
> git remote prune origin
> 
> Other than that -- looks good to me.
> 
> D.
> 
> On Wed, Mar 10, 2021 at 11:19 PM Jan Høydahl  wrote:
>> 
>> Yep, I updated it with a check that the command succeeded.
>> 
>> Jan
>> 
>> 10. mar. 2021 kl. 23:09 skrev Ilan Ginzburg :
>> 
>> Any risk in the script that command:
>> git push ${REMOTE} 
>> cominvent/$BRANCH:refs/tags/history/branches/lucene-solr/$BRANCH
>> errors out in some exotic way (?) but the script continues anyway and 
>> proceeds with the delete:
>> git push ${REMOTE} --delete $BRANCH
>> 
>> 
>> On Wed, Mar 10, 2021 at 10:35 PM Jan Høydahl  wrote:
>>> 
>>> Ok, I took a stab at this
>>> 
>>> We have 113 branches. Here is a script I prepared that will work directly 
>>> on a git remote, first creating the tag then deleting the branch.
>>> https://gist.github.com/80a7eea6bacd4e32646a7958d1e9a870
>>> 
>>> In the script I have added the list of branches that I propose to "archive".
>>> 
>>> Below that there is a commented section of branches that are reported as 
>>> "active" by GitHub that should probably stay for now
>>> Finally, we have some branches we might want to keep around for refernce?
>>> I'm not sure how useful it is to keep a branch in solr.git for, say 
>>> branch_8_8, as it will fall behind as branch_8_8 in lucene-solr.git gets 
>>> updated. So probably archive those as well?
>>> 
>>> The pure lucene branches like LUCENE-9004 won't need a tag at all I 
>>> suppose, but it won't hurt either.
>>> 
>>> Jan
>>> 
 10. mar. 2021 kl. 21:16 skrev Dawid Weiss :
 
> We already did this before, see list of existing tags (git tag -l)
 
 I know, I did it, after all... :) This was a move from subversion
 though... slightly different. Anyway - if you guys want to proceed
 with this, please go ahead, I don't mind. A spring cleaning is needed
 every couple of years... If we just leave the main branch it'll be
 very elegant. People work on their local repos these days anyway, it's
 not like everyone pollutes the same workspace.
 
 D.
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
 For additional commands, e-mail: dev-h...@lucene.apache.org
 
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>> 
>> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Branch cleaning/ archiving

[Dawid Weiss]

This will also require people who already made their clones/ forks to
prune their copy of the remote as this isn't done automatically.

git remote prune origin

Other than that -- looks good to me.

D.

On Wed, Mar 10, 2021 at 11:19 PM Jan Høydahl  wrote:
>
> Yep, I updated it with a check that the command succeeded.
>
> Jan
>
> 10. mar. 2021 kl. 23:09 skrev Ilan Ginzburg :
>
> Any risk in the script that command:
> git push ${REMOTE} 
> cominvent/$BRANCH:refs/tags/history/branches/lucene-solr/$BRANCH
> errors out in some exotic way (?) but the script continues anyway and 
> proceeds with the delete:
> git push ${REMOTE} --delete $BRANCH
>
>
> On Wed, Mar 10, 2021 at 10:35 PM Jan Høydahl  wrote:
>>
>> Ok, I took a stab at this
>>
>> We have 113 branches. Here is a script I prepared that will work directly on 
>> a git remote, first creating the tag then deleting the branch.
>> https://gist.github.com/80a7eea6bacd4e32646a7958d1e9a870
>>
>> In the script I have added the list of branches that I propose to "archive".
>>
>> Below that there is a commented section of branches that are reported as 
>> "active" by GitHub that should probably stay for now
>> Finally, we have some branches we might want to keep around for refernce?
>> I'm not sure how useful it is to keep a branch in solr.git for, say 
>> branch_8_8, as it will fall behind as branch_8_8 in lucene-solr.git gets 
>> updated. So probably archive those as well?
>>
>> The pure lucene branches like LUCENE-9004 won't need a tag at all I suppose, 
>> but it won't hurt either.
>>
>> Jan
>>
>> > 10. mar. 2021 kl. 21:16 skrev Dawid Weiss :
>> >
>> >> We already did this before, see list of existing tags (git tag -l)
>> >
>> > I know, I did it, after all... :) This was a move from subversion
>> > though... slightly different. Anyway - if you guys want to proceed
>> > with this, please go ahead, I don't mind. A spring cleaning is needed
>> > every couple of years... If we just leave the main branch it'll be
>> > very elegant. People work on their local repos these days anyway, it's
>> > not like everyone pollutes the same workspace.
>> >
>> > D.
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> > For additional commands, e-mail: dev-h...@lucene.apache.org
>> >
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>
>

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Welcome Bruno to the Apache Lucene PMC

[Adrien Grand]

Welcome Bruno!

On Thu, Mar 11, 2021 at 2:39 AM Michael Sokolov  wrote:

> Welcome, Bruno!
>
> On Wed, Mar 10, 2021, 7:56 PM Mike Drob  wrote:
>
>> I am pleased to announce that Bruno has accepted an invitation to join
>> the Lucene PMC!
>>
>> Congratulations, and welcome aboard!
>>
>> Mike
>>
>

-- 
Adrien

Re: Welcome Bruno to the Apache Lucene PMC

[Michael Sokolov]

Welcome, Bruno!

On Wed, Mar 10, 2021, 7:56 PM Mike Drob  wrote:

> I am pleased to announce that Bruno has accepted an invitation to join the
> Lucene PMC!
>
> Congratulations, and welcome aboard!
>
> Mike
>

Re: Lucene and Solr repositories mirrored, main branch ready

[Michael Sokolov]

Big thank you, Dawid, and Jan and others for taking the bull by the horns!

On Wed, Mar 10, 2021, 3:14 PM Dawid Weiss  wrote:

> > Just tested out the main branch of the new repo, packaged, started,
> loaded data, searched from the UI. All looks great.
>
> Thank you, great to know!
>
> Dawid
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

Welcome Bruno to the Apache Lucene PMC

[Mike Drob]

I am pleased to announce that Bruno has accepted an invitation to join the
Lucene PMC!

Congratulations, and welcome aboard!

Mike

Re: Branch cleaning/ archiving

[Jan Høydahl]

Yep, I updated it with a check that the command succeeded.

Jan

> 10. mar. 2021 kl. 23:09 skrev Ilan Ginzburg :
> 
> Any risk in the script that command:
> git push ${REMOTE} 
> cominvent/$BRANCH:refs/tags/history/branches/lucene-solr/$BRANCH
> errors out in some exotic way (?) but the script continues anyway and 
> proceeds with the delete:
> git push ${REMOTE} --delete $BRANCH
> 
> 
> On Wed, Mar 10, 2021 at 10:35 PM Jan Høydahl  > wrote:
> Ok, I took a stab at this
> 
> We have 113 branches. Here is a script I prepared that will work directly on 
> a git remote, first creating the tag then deleting the branch.
> https://gist.github.com/80a7eea6bacd4e32646a7958d1e9a870 
> 
> 
> In the script I have added the list of branches that I propose to "archive".
> 
> Below that there is a commented section of branches that are reported as 
> "active" by GitHub that should probably stay for now
> Finally, we have some branches we might want to keep around for refernce?
> I'm not sure how useful it is to keep a branch in solr.git for, say 
> branch_8_8, as it will fall behind as branch_8_8 in lucene-solr.git gets 
> updated. So probably archive those as well?
> 
> The pure lucene branches like LUCENE-9004 won't need a tag at all I suppose, 
> but it won't hurt either.
> 
> Jan
> 
> > 10. mar. 2021 kl. 21:16 skrev Dawid Weiss  > >:
> > 
> >> We already did this before, see list of existing tags (git tag -l)
> > 
> > I know, I did it, after all... :) This was a move from subversion
> > though... slightly different. Anyway - if you guys want to proceed
> > with this, please go ahead, I don't mind. A spring cleaning is needed
> > every couple of years... If we just leave the main branch it'll be
> > very elegant. People work on their local repos these days anyway, it's
> > not like everyone pollutes the same workspace.
> > 
> > D.
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org 
> > 
> > For additional commands, e-mail: dev-h...@lucene.apache.org 
> > 
> > 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org 
> 
> For additional commands, e-mail: dev-h...@lucene.apache.org 
> 
> 

Re: Branch cleaning/ archiving

[Ilan Ginzburg]

Any risk in the script that command:
git push ${REMOTE}
cominvent/$BRANCH:refs/tags/history/branches/lucene-solr/$BRANCH
errors out in some exotic way (?) but the script continues anyway and
proceeds with the delete:
git push ${REMOTE} --delete $BRANCH


On Wed, Mar 10, 2021 at 10:35 PM Jan Høydahl  wrote:

> Ok, I took a stab at this
>
> We have 113 branches. Here is a script I prepared that will work directly
> on a git remote, first creating the tag then deleting the branch.
> https://gist.github.com/80a7eea6bacd4e32646a7958d1e9a870
>
> In the script I have added the list of branches that I propose to
> "archive".
>
> Below that there is a commented section of branches that are reported as
> "active" by GitHub that should probably stay for now
> Finally, we have some branches we might want to keep around for refernce?
> I'm not sure how useful it is to keep a branch in solr.git for, say
> branch_8_8, as it will fall behind as branch_8_8 in lucene-solr.git gets
> updated. So probably archive those as well?
>
> The pure lucene branches like LUCENE-9004 won't need a tag at all I
> suppose, but it won't hurt either.
>
> Jan
>
> > 10. mar. 2021 kl. 21:16 skrev Dawid Weiss :
> >
> >> We already did this before, see list of existing tags (git tag -l)
> >
> > I know, I did it, after all... :) This was a move from subversion
> > though... slightly different. Anyway - if you guys want to proceed
> > with this, please go ahead, I don't mind. A spring cleaning is needed
> > every couple of years... If we just leave the main branch it'll be
> > very elegant. People work on their local repos these days anyway, it's
> > not like everyone pollutes the same workspace.
> >
> > D.
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> > For additional commands, e-mail: dev-h...@lucene.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

Re: Does CVE-2020-27223 impact Solr 8.6.1

[Jan Høydahl]

Hi,

Please see https://solr.apache.org/security.html for how to handle potential 
security issues responsibly.
From time to time we upgrade our Jetty dependencies, so feel free to file a 
public JIRA to upgrade Jetty in next release.
Normally you'd not be vulnerable to this DoS attach since you would of course 
not expose the Solr servers to the internet or other hostile networks...

Jan

> 10. mar. 2021 kl. 22:12 skrev Steven White :
> 
> Hi everyone,
> 
> Sorry for the double post, as I posted this on the Solr mailing list too.
> 
> Does anyone know if CVE-2020-27223 [1] impacts Solr?  This is a vulnerability 
> in jetty-http-9.4.27.v20200227.jar which we ship with Solr 8.6.1.
> 
> Thanks,
> 
> Steven
> 
> [1] https://nvd.nist.gov/vuln/detail/CVE-2020-27223 
> 

Re: Branch cleaning/ archiving

[Jan Høydahl]

Ok, I took a stab at this

We have 113 branches. Here is a script I prepared that will work directly on a 
git remote, first creating the tag then deleting the branch.
https://gist.github.com/80a7eea6bacd4e32646a7958d1e9a870

In the script I have added the list of branches that I propose to "archive".

Below that there is a commented section of branches that are reported as 
"active" by GitHub that should probably stay for now
Finally, we have some branches we might want to keep around for refernce?
I'm not sure how useful it is to keep a branch in solr.git for, say branch_8_8, 
as it will fall behind as branch_8_8 in lucene-solr.git gets updated. So 
probably archive those as well?

The pure lucene branches like LUCENE-9004 won't need a tag at all I suppose, 
but it won't hurt either.

Jan

> 10. mar. 2021 kl. 21:16 skrev Dawid Weiss :
> 
>> We already did this before, see list of existing tags (git tag -l)
> 
> I know, I did it, after all... :) This was a move from subversion
> though... slightly different. Anyway - if you guys want to proceed
> with this, please go ahead, I don't mind. A spring cleaning is needed
> every couple of years... If we just leave the main branch it'll be
> very elegant. People work on their local repos these days anyway, it's
> not like everyone pollutes the same workspace.
> 
> D.
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Branch cleaning/ archiving

[David Smiley]

On Wed, Mar 10, 2021 at 3:17 PM Dawid Weiss  wrote:

> ...People work on their local repos these days anyway, it's
> not like everyone pollutes the same workspace.
>

I very much concur.  When I got started with git, I treated it closer to
what I was previously more familiar with and created branches upstream in
the main repo.  Now I know better -- I use my fork.

If a branch hasn't received a commit in > 2 years, we might auto-purge them
and do this practice regularly.  Before auto-purge, we could even list the
people who last did a commit on the branches to let them know.  With that
notification system, even more regular purges would be good.

Does CVE-2020-27223 impact Solr 8.6.1

[Steven White]

Hi everyone,

Sorry for the double post, as I posted this on the Solr mailing list too.

Does anyone know if CVE-2020-27223 [1] impacts Solr?  This is a
vulnerability in jetty-http-9.4.27.v20200227.jar which we ship with Solr
8.6.1.

Thanks,

Steven

[1] https://nvd.nist.gov/vuln/detail/CVE-2020-27223

Re: Branch cleaning/ archiving

[Dawid Weiss]

> We already did this before, see list of existing tags (git tag -l)

I know, I did it, after all... :) This was a move from subversion
though... slightly different. Anyway - if you guys want to proceed
with this, please go ahead, I don't mind. A spring cleaning is needed
every couple of years... If we just leave the main branch it'll be
very elegant. People work on their local repos these days anyway, it's
not like everyone pollutes the same workspace.

D.

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Lucene and Solr repositories mirrored, main branch ready

[Dawid Weiss]

> Just tested out the main branch of the new repo, packaged, started, loaded 
> data, searched from the UI. All looks great.

Thank you, great to know!

Dawid

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Lucene and Solr repositories mirrored, main branch ready

[Joel Bernstein]

Just tested out the main branch of the new repo, packaged, started, loaded
data, searched from the UI. All looks great. Very exciting! Thanks Dawid
for all your work on this!


Joel Bernstein
http://joelsolr.blogspot.com/


On Wed, Mar 10, 2021 at 10:14 AM Atri Sharma  wrote:

> Totally agreed. They have really driven this to completion with as minimal
> disruption as possible.
>
> Special mention to Uwe, as always!
>
> On Wed, 10 Mar 2021, 20:32 David Smiley,  wrote:
>
>> Thank *you* Dawid!  You and Jan have been big heroes of this transition!
>>
>> ~ David Smiley
>> Apache Lucene/Solr Search Developer
>> http://www.linkedin.com/in/davidwsmiley
>>
>>
>> On Wed, Mar 10, 2021 at 9:36 AM Dawid Weiss 
>> wrote:
>>
>>> Thank you everyone for the collective effort to clean up stale project
>>> references, templates, etc.
>>>
>>> D.
>>>
>>> On Wed, Mar 10, 2021 at 1:04 PM Dawid Weiss 
>>> wrote:
>>> >
>>> > First of all, apologies for the e-mail commit bomb... Things like that
>>> > can happen, hard to tell in advance. Thanks to infra for helping out.
>>> >
>>> > Solr and Lucene repositories have been cloned at commit 7ada403218.
>>> >
>>> > Master branch is wiped out of content on all repositories, branch_8x
>>> > is wiped on lucene and solr repositories to avoid confusion (8x
>>> > development takes place at the joint repository).
>>> >
>>> > I've removed lucene/solr from each other. Things should work out of
>>> > the box but if something does not, please file an issue (or better -
>>> > try to fix it).
>>> >
>>> > There is going to be a lot of mundane cleanup work to remove cross
>>> > references and get the documentation going but it's all a follow-up.
>>> >
>>> > Here is a short help guide to port existing PRs:
>>> > https://github.com/apache/lucene-solr/blob/master/PRs.md
>>> >
>>> > Github actions should work too, as shown here:
>>> > https://github.com/apache/lucene/pull/2
>>> >
>>> > Builds can be enabled (perhaps slowly, at first? :).
>>> >
>>> > Solr developers: Lucene can be built and installed in your local maven
>>> > repositories with:
>>> > gradlew mavenToLocalRepo
>>> >
>>> > Dawid
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>>
>>>

RE: Branch cleaning/ archiving

[Uwe Schindler]

Hi,

we discussed the tagging already on Slack. That was exactly Jan's and my 
proposal. Can be scripted.

This should mainly done for branches that are definitely outdated. We can for 
example script this after creating a list of branches that should be removed. 
We won't loose history, because we have all references still in the repo, we 
just want to get rid of those to prevent people from doing wrong things: E.g., 
somebody gets low sugar status and does not know which origin to push to. A 
"not found" error is better than no longer knowing if branch_8x should live on 
repo "a" or repo "b"! In addition, if branch does not exist, wrongly configured 
jenkins jobs wont run!

BTW, we did the same with old branches and tags after the switched from 
subversion to git. Branches are no longer there, but we still have tags under 
"history/".

FYI, I purged the "master" branch in the new repos after INFRA changed the HEAD 
on github and gitbox. If somebody clones our (new) repos, heshe get's "main" by 
default. Thanks to Infra for manually changing the "HEAD" link on the bare 
gitbox and Github repos (which survives also branch deletes and would have been 
detached after master was nuked).

-
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:13 PM
> To: Lucene Dev 
> Subject: Branch cleaning/ archiving
> 
> I know Uwe wants to purge some (or all) of the existing branches...
> I'm not really fond of removing them - this sort of misses the point
> of pushing the full mirror from the old repo.
> 
> I do understand the will to clean up, however... Maybe we can tag all
> existing branches under a common prefix (archive/lucene-solr/*) and
> then delete those branch refs? Would this be fine, Uwe?
> 
> Dawid
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Branch cleaning/ archiving

[Jan Høydahl]

+1 to tag and remove most if not all branches.

We already did this before, see list of existing tags (git tag -l)

...
history/branches/lucene-solr/lucene_solr_3_1
history/branches/lucene-solr/lucene_solr_3_2
history/branches/lucene-solr/lucene_solr_3_3
history/branches/lucene-solr/lucene_solr_3_4
history/branches/lucene-solr/lucene_solr_3_5
...
history/branches/lucene-solr/starburst
history/branches/lucene-solr/throwawaybranch
history/branches/solr/branch-1.3
...

Jan

> 10. mar. 2021 kl. 20:12 skrev Dawid Weiss :
> 
> I know Uwe wants to purge some (or all) of the existing branches...
> I'm not really fond of removing them - this sort of misses the point
> of pushing the full mirror from the old repo.
> 
> I do understand the will to clean up, however... Maybe we can tag all
> existing branches under a common prefix (archive/lucene-solr/*) and
> then delete those branch refs? Would this be fine, Uwe?
> 
> Dawid
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
> 

Branch cleaning/ archiving

[Dawid Weiss]

I know Uwe wants to purge some (or all) of the existing branches...
I'm not really fond of removing them - this sort of misses the point
of pushing the full mirror from the old repo.

I do understand the will to clean up, however... Maybe we can tag all
existing branches under a common prefix (archive/lucene-solr/*) and
then delete those branch refs? Would this be fine, Uwe?

Dawid

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Lucene and Solr repositories mirrored, main branch ready

[Atri Sharma]

Totally agreed. They have really driven this to completion with as minimal
disruption as possible.

Special mention to Uwe, as always!

On Wed, 10 Mar 2021, 20:32 David Smiley,  wrote:

> Thank *you* Dawid!  You and Jan have been big heroes of this transition!
>
> ~ David Smiley
> Apache Lucene/Solr Search Developer
> http://www.linkedin.com/in/davidwsmiley
>
>
> On Wed, Mar 10, 2021 at 9:36 AM Dawid Weiss  wrote:
>
>> Thank you everyone for the collective effort to clean up stale project
>> references, templates, etc.
>>
>> D.
>>
>> On Wed, Mar 10, 2021 at 1:04 PM Dawid Weiss 
>> wrote:
>> >
>> > First of all, apologies for the e-mail commit bomb... Things like that
>> > can happen, hard to tell in advance. Thanks to infra for helping out.
>> >
>> > Solr and Lucene repositories have been cloned at commit 7ada403218.
>> >
>> > Master branch is wiped out of content on all repositories, branch_8x
>> > is wiped on lucene and solr repositories to avoid confusion (8x
>> > development takes place at the joint repository).
>> >
>> > I've removed lucene/solr from each other. Things should work out of
>> > the box but if something does not, please file an issue (or better -
>> > try to fix it).
>> >
>> > There is going to be a lot of mundane cleanup work to remove cross
>> > references and get the documentation going but it's all a follow-up.
>> >
>> > Here is a short help guide to port existing PRs:
>> > https://github.com/apache/lucene-solr/blob/master/PRs.md
>> >
>> > Github actions should work too, as shown here:
>> > https://github.com/apache/lucene/pull/2
>> >
>> > Builds can be enabled (perhaps slowly, at first? :).
>> >
>> > Solr developers: Lucene can be built and installed in your local maven
>> > repositories with:
>> > gradlew mavenToLocalRepo
>> >
>> > Dawid
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>
>>

Re: Lucene and Solr repositories mirrored, main branch ready

[David Smiley]

Thank *you* Dawid!  You and Jan have been big heroes of this transition!

~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley


On Wed, Mar 10, 2021 at 9:36 AM Dawid Weiss  wrote:

> Thank you everyone for the collective effort to clean up stale project
> references, templates, etc.
>
> D.
>
> On Wed, Mar 10, 2021 at 1:04 PM Dawid Weiss  wrote:
> >
> > First of all, apologies for the e-mail commit bomb... Things like that
> > can happen, hard to tell in advance. Thanks to infra for helping out.
> >
> > Solr and Lucene repositories have been cloned at commit 7ada403218.
> >
> > Master branch is wiped out of content on all repositories, branch_8x
> > is wiped on lucene and solr repositories to avoid confusion (8x
> > development takes place at the joint repository).
> >
> > I've removed lucene/solr from each other. Things should work out of
> > the box but if something does not, please file an issue (or better -
> > try to fix it).
> >
> > There is going to be a lot of mundane cleanup work to remove cross
> > references and get the documentation going but it's all a follow-up.
> >
> > Here is a short help guide to port existing PRs:
> > https://github.com/apache/lucene-solr/blob/master/PRs.md
> >
> > Github actions should work too, as shown here:
> > https://github.com/apache/lucene/pull/2
> >
> > Builds can be enabled (perhaps slowly, at first? :).
> >
> > Solr developers: Lucene can be built and installed in your local maven
> > repositories with:
> > gradlew mavenToLocalRepo
> >
> > Dawid
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

Re: Lucene and Solr repositories mirrored, main branch ready

[Dawid Weiss]

Thank you everyone for the collective effort to clean up stale project
references, templates, etc.

D.

On Wed, Mar 10, 2021 at 1:04 PM Dawid Weiss  wrote:
>
> First of all, apologies for the e-mail commit bomb... Things like that
> can happen, hard to tell in advance. Thanks to infra for helping out.
>
> Solr and Lucene repositories have been cloned at commit 7ada403218.
>
> Master branch is wiped out of content on all repositories, branch_8x
> is wiped on lucene and solr repositories to avoid confusion (8x
> development takes place at the joint repository).
>
> I've removed lucene/solr from each other. Things should work out of
> the box but if something does not, please file an issue (or better -
> try to fix it).
>
> There is going to be a lot of mundane cleanup work to remove cross
> references and get the documentation going but it's all a follow-up.
>
> Here is a short help guide to port existing PRs:
> https://github.com/apache/lucene-solr/blob/master/PRs.md
>
> Github actions should work too, as shown here:
> https://github.com/apache/lucene/pull/2
>
> Builds can be enabled (perhaps slowly, at first? :).
>
> Solr developers: Lucene can be built and installed in your local maven
> repositories with:
> gradlew mavenToLocalRepo
>
> Dawid

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Lucene and Solr repositories mirrored, main branch ready

[Dawid Weiss]

First of all, apologies for the e-mail commit bomb... Things like that
can happen, hard to tell in advance. Thanks to infra for helping out.

Solr and Lucene repositories have been cloned at commit 7ada403218.

Master branch is wiped out of content on all repositories, branch_8x
is wiped on lucene and solr repositories to avoid confusion (8x
development takes place at the joint repository).

I've removed lucene/solr from each other. Things should work out of
the box but if something does not, please file an issue (or better -
try to fix it).

There is going to be a lot of mundane cleanup work to remove cross
references and get the documentation going but it's all a follow-up.

Here is a short help guide to port existing PRs:
https://github.com/apache/lucene-solr/blob/master/PRs.md

Github actions should work too, as shown here:
https://github.com/apache/lucene/pull/2

Builds can be enabled (perhaps slowly, at first? :).

Solr developers: Lucene can be built and installed in your local maven
repositories with:
gradlew mavenToLocalRepo

Dawid

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: [DISCUSS] Sunset the general@l.a.o mailing list?

[Jan Høydahl]

Email to list was sent 
https://lists.apache.org/thread.html/re7ffb4329bfe916d7e5a4ac1cb31c9118ad738136daaf5df01688b95%40%3Cgeneral.lucene.apache.org%3E
List not announced on web site anymore 
https://lucene.apache.org/core/discussion.html#retired-mailing-lists
INFRA asked to archive the list 
https://issues.apache.org/jira/browse/INFRA-21550

Some stats from last 12 months:
- 71 emails sent by 47 people
- 31 of those are relase ANNOUNCE mails
- 8 are Pylycene VOTE mails (2 threads)
- 2 are CVE announce mails
- 4 just random / ads / info
- 11 are user questions about Solr that should have been in solr-user@

RIP general@

Jan

> 8. mar. 2021 kl. 18:28 skrev Jan Høydahl :
> 
> Yep, that's on my plan.
> 
> Jan
> 
>> 8. mar. 2021 kl. 17:56 skrev Michael Sokolov :
>> 
>> maybe send an email to the list informing anyone who's listening?
>> 
>> On Mon, Mar 8, 2021 at 8:07 AM Jan Høydahl  wrote:
>>> 
>>> It's been one week, and there were 5 respondents. Three explicitly in 
>>> favour of sunsetting the list.
>>> This was not a VOTE, but I'll interpret the response as lazy consensus, and 
>>> proceed with removing the mention of the list on the website today.
>>> 
>>> Is there some step to take to shut the list down so it won't accept emails? 
>>> I can open an INFRA ticker. However, I'll wait another 2 days before doing 
>>> so.
>>> 
>>> Jan
>>> 
 28. feb. 2021 kl. 22:02 skrev Jan Høydahl :
 
 Hi
 
 The general@ list is not being used for practically anything. I see some 
 user questions there and we announce releases. It may have had more 
 purpose when there were 5 sub projects in Lucene. Now it is more confusing 
 users and they do not get timely replies. The list has 1088 subscribers.
 
 I propose to discontinue the list, i.e. make it Read-Only and remove it 
 from the web page. Anyone who would miss it?
 
 Jan Høydahl
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: dev-h...@lucene.apache.org
>> 
> 


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

RE: Repository fork (master) about to happen (Wednesday)

[Uwe Schindler]

“Master” builds are disabled on ASF Jenkins and Policeman Jenkins.

 

Uwe

 

-

Uwe Schindler

Achterdiek 19, D-28357 Bremen

  https://www.thetaphi.de

eMail: u...@thetaphi.de

 

From: Uwe Schindler  
Sent: Tuesday, March 9, 2021 4:47 PM
To: dev@lucene.apache.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   mailing list for build 
mails. I also cleaned up some outdated jobs. As Jenkins’ address is not 
subscribed to bui...@solr.apache.org   (and 
never should be subscribed), the address may need to be put on the “accept” 
list. So this is important information for the moderators: If a build mail goes 
into moderation, somebody of the moderators has to use “reply all” to let it 
through (reply-all automatically adds mail to the whitelist).

 

This must be done for policeman jenkins, too, but I am not sure about ASF 
jenkins! It looks like most mailinglists have an auto-whitelist for all 
@apache.org addresses.

 

Uwe

 

-

Uwe Schindler

Achterdiek 19, D-28357 Bremen

  https://www.thetaphi.de

eMail: u...@thetaphi.de  

 

From: Uwe Schindler mailto:u...@thetaphi.de> > 
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

 

-

Uwe Schindler

Achterdiek 19, D-28357 Bremen

  https://www.thetaphi.de

eMail: u...@thetaphi.de  

 

From: Dawid Weiss mailto:dawid.we...@gmail.com> > 
Sent: Tuesday, March 9, 2021 9:01 AM
To: Lucene Dev mailto:dev@lucene.apache.org> >
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 
convenience, thank you Uwe.

 

Yes. Basically, we can duplicate the jobs and run the same command, just with 
different Git checkout. This needs to be done on ASF Jenkins and Policeman 
Jenkins.

 

Correct. Initially it'll be identical. In the future I think it'd be good to 
pull up modules from under 'lucene' up to the root folder but this isn't a 
trivial change as project and task paths are all over the build and it should 
be a follow-up.

 

 

 

Ah, my friend. I wish we could do this in person.

 

D. 

RE: Repository fork (master) about to happen (Wednesday)

[Uwe Schindler]

+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 happen (Wednesday)
> 
> > 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 repositories.
> 
> D.
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org