Maybe we can get a dedicated open source code review bot and tweak it’s code for us. That should instill more confidence :)
> On Sep 2, 2026, at 8:02 PM, David Smiley <[email protected]> wrote: > > It's never been an easier time as a committer to be the shepherd/reviewer > to a non-committer PR. We have automated code reviews via GitHub co-pilot > (need to add as a reviewer to engage). No longer do we have to edit a > massive CHANGES.txt to pick a version that might be wrong or even know the > version. No longer do we have the chore of back-porting, for the vast > majority of PRs. Just pick a final destination Milestone on the PR and > please DM me a "thank you" if you appreciate this. An LLM armed with a > script is usually going to do this more thoroughly than you would have > (i.e. it actually considers multiple CI jobs and usually runs tests before > push). And recently, I'll manually "resolve" the JIRA issue as well as the > final step (if it looks like a one-shot PR issue) -- Eric cleverly > convinced me I wasn't doing enough, so I've got this ;-). It's really > rather satisfying. > > So with that said, I want to ask the committers here that don't review > other people's PRs to please do so, especially those of contributors. You > have powers they don't -- you can get something merged. The contributor > will be grateful; remember being in their shoes. You can fully handle a PR > responsiby without leaving the GitHub PR issue screen -- at least most of > the time. > > p.s. I'm also grateful for Crave.io for very fast builds... but we'll need > to do without this by the end of the year :-( > > ~ David Smiley > Apache Lucene/Solr Search Developer > http://www.linkedin.com/in/davidwsmiley --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
