Thank you for the replies so far.
I think that each contrib would necessarily have to have their own release
schedule and release vote. I suspect that there might be frequent releases
at first, and then these will smooth out into basically once per major
release. I also think that contribs having
Thanks for sending this email, Mike and thanks for the follow up, David.
The idea of having multiple repos under the project seems like the
reasonable way to go for our project. This allows us to support more
features/tooling/etc. without having to link them to Solr or Lucene
releases.
An
STUniformSplitPostingsFormat is used in production at a massive scale,
helping reduce overall memory needs a ton. I highly recommend it :-)
notwithstanding the main caveat of any non-default format:
"lucene.experimental" can be applied for different reasons -- the main one
is
We should fix these build notification emails where the subject says
"failing" and then the subject says "All tests passed" :)
In this case it was javadoc linting issue.
Unfortunately, I think to fix this we have to edit the most horrific regexp
I've ever seen, that Jenkins uses to extract what
Mike S pushed a fix for this this AM (EST!).
Mike McCandless
http://blog.mikemccandless.com
On Tue, Nov 17, 2020 at 10:08 AM Policeman Jenkins Server <
jenk...@thetaphi.de> wrote:
> Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/28665/
> Java: 64bit/jdk-13.0.2
