To everyone following this e-mail thread.
The Project Management Committees have discussed the matter and would like to
draw attention to "Statement from the Solr and Lucene PMC regarding recent Code
of Conduct violations" posted to this list today, and linked below:
I apologize for the harsh words, and personally to Andrzej for hurting your
feelings. I had no such intentions.
> You conveniently don’t mention that I WITHDREW my objection, and instead
proposed a lenient validation (but validation nonetheless!).
Yes, let me mention that you agreed in principal
Hi AB,
Please accept my I apologies for the heated discussion. The objective
was not that at all.
I saw the real damage that was caused to our client. It was
devastating. We were a little worried about the same happening to
another user who might upgrade.
So, I suggested a revert.
Whatever
Ishan, as I pointed out in Jira I don’t care for you implying that I have evil
intentions, I resent also your implication that I’m behaving irrationally or
don’t care for the users. Those of you who are interested may read the comments
in Jira and judge for themselves.
You conveniently don’t
I have some thoughts, if I may please stop acting so quickly and
*violently* at every annoyance you have around here. Your trigger finger and
attitude, -Ishan- are disruptive to _community_ and lack the basic tactful
pleasantries.
Calling a respected, and quite long time badass
https://issues.apache.org/jira/browse/SOLR-14245
There was a *production outage* at *odd hours* at my (and Noble's) client,
due to this above change in Solr 8.5 onwards by *Andrzej Bialecki*.
In short, there is some bug in Solr where a replica gets "null" as the
node_name (upon invocation of a
