chatman commented on PR #3053:
URL: https://github.com/apache/solr/pull/3053#issuecomment-3165232514

   > But I've got to say, it's premature to merge a PR without either first 
seeking and getting another approval or to state your intention to merge in 48 
hours. This isn't a triival PR (of course). I don't want other committers (esp. 
new ones) or contributors to think this is normal. It's not. The same thing 
happened with the multiThreaded PR, which didn't turn out well, as you know.
   
   Apache Solr still follows CTR policy [0]. If anyone has an objection, I'll 
revert my commits. This is the traditional process. This is not a trivial PR 
(of course), and I can't keep up with all the changes that keep happening on 
main.
   
   When there were failures on this branch, it was my problem (and Christine's 
and Jason's too). You can scroll up and review the comments. Now, after this 
merge, all problems out of this merge is a collective problem (which is good, 
IMHO).
   
   > The same thing happened with the multiThreaded PR, which didn't turn out 
well, as you know.
   If you want to blame me for something, I can as well blame others for the 
sorry state of affairs this project is currently in. This is not healthy. I'm 
back to Solr development to make things better, not blame others for past 
issues.
   
   [0] - https://infra.apache.org/new-committers-guide.html#the-committers-way


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to