+1
Met vriendelijke groeten,
Marc Jeurissen
Bibliotheek UAntwerpen
Stadscampus – Ve35.303
Venusstraat 35 – 2000 Antwerpen
marc.jeuris...@uantwerpen.be
T +32 3 265 49 71
From: Andi Vajda
Sent: maandag 4 november 2019 2:54
To: pylucene-dev@lucene.apache.org
Cc: gene...@lucene.apache.org
The PyLucene 8.3.0 (rc1) release tracking the recent release of
Apache Lucene 8.3.0 is ready.
A release candidate is available from:
https://dist.apache.org/repos/dist/dev/lucene/pylucene/8.3.0-rc1/
PyLucene 8.3.0 is built with JCC 3.7, included in these release artifacts.
JCC 3.7 supports
* I have not been able to SELL yet.
On Sun, Nov 3, 2019 at 6:50 PM Mark Miller wrote:
> BUT .. it's in reasonable shape. More things should be done. Reduce
> unnecessary dependencies between projects - we want to avoid as much
> circular nonsense as we can. Other stuff. You might want to drop
BUT .. it's in reasonable shape. More things should be done. Reduce
unnecessary dependencies between projects - we want to avoid as much
circular nonsense as we can. Other stuff. You might want to drop some
things I have not been able to see yet.
But the latest like 8 branch is super nice for a
here is a bug i cannot shake in when building lucne/site
inside lucene/src/main/xml/ENTITY_TermQuery.xml
http://www.bar.xyz/external;>
http://www.bar.xyz/param;>
using ant build.xml:
OR maven pom.xml
In my opinion it would have been better to delay the release announcement
another day in order to collect release-notes feedback, than to rush it out.
But apology is accepted :) Being RM during such a stressful week is not ideal.
You did well.
Looking forward to more detailed feedback regarding
> according to lucene’s release todo the rm must send a [RESULT][VOTE] email.
You're wrong.
The Lucene's Release TODO page says this:
"Announce that the vote has passed on the dev mailing list, ideally
with subject beginning [RESULT]"
^ I did announce on dev list that the vote passed. It wasn't
Thanks Jan, for the encouragement and for the release wizard tool.
All of last week, I was battling several personal emergencies as well as
professional responsibilities. I was so short on time that I cut some
corners (in the following two places), *deliberately*.
1. I checked how often have we
And the bummer is, in the midst of this madness people are doing good work.
Good cleanups. Good improvements. Good features. Good code. And it’s all
basically wasted. It’s my hurts my mind.
Mark
On Sun, Nov 3, 2019 at 7:58 AM Mark Miller wrote:
> From a credentials standpoint:
>
> Yonik and I
>From a credentials standpoint:
Yonik and I built 90% of it originally and then I spent years on it with
few other devs or users.
Pretty sure I'm the only one that has ever had 95%+ of the Solr test suites
work in under 10-15 seconds consistently - 4000 tests across like 1000
suites. Got them
Personally, I believe the latter so strongly, if I can’t convince the
others in the raft with me, I’m jumping in and swimming to another raft
after my entire adult life here.
Mark
On Sun, Nov 3, 2019 at 7:30 AM Mark Miller wrote:
> In fact this will be a fundamental difference some of us are
In fact this will be a fundamental difference some of us are about to split
between.
Those that think they can ever fix the tests or the system or the 1000s of
bugs we have and keep adding due to our current world view of making tests
fit the system not the system fit the tests and that fact that
bq. They also would allow it to do it in an iterative manner without
changing everything at once.
Sadly, you can't fix this piece by piece :) I dare anyone to try. I
encourage, I applaud the effort.
The world is your oyster from a good spot - take your pick of how to do
things.
But from this
Don’t know that I’ll be around yet in the future so I’m not going to make
such a big change myself.
Mark
On Sun, Nov 3, 2019 at 12:29 AM David Smiley
wrote:
> What's the status of this Mark? Sorry to ask but someone had to. It's
> obvious your attention is on a big Solr effort right now but
I cannot say anything about the statements, but maybe it could help to
introduce Solr Improvement Proposals (SIP) similar to Kafka Improvement
Proposals (KIP) or Flink Improvement Proposals (FLIP).
I think they are helpful to facilitate design decisions and refactoring /
redesign decision.
Ishan,
Congrats with the release!
I may have missed it, but where were the draft release notes for review and
comments, I was waiting for an invitation...
And how many +1 PMC votes were there? I’m not in doubt that the vote passed,
but according to lucene’s release todo the rm must send a
16 matches
Mail list logo
