News for hackers. Stuff that matters.

A comment on Readyset: A MySQL and Postgres wire-compatible caching layer. Parent comment

Re:Readyset: A MySQL and Postgres wire-compatible caching layer by hobofan on Wednesday February 21, 2024 @10:48AM (#39455249)
I don't think it's fair to hold the number of open issues and pull requests against them. Looking through them for a minute, it looks like 95%+ are from their own team members, with a good chunk of the issues being "low priority" issues. So you are just seeing the typical ever-growing backlog that is normally in a private JIRA instance.

Having said that, the way they work with pull requests is unlike anything else I've seen. I see that they are using a merge bot, but apart from that all branch names are completely illegible. As a lot of the team seems to be present in this thread, it would be interesting to get some details about that.

[ Parent | on HN ]
Re:Readyset: A MySQL and Postgres wire-compatible caching layer by lukoktonos on Wednesday February 21, 2024 @11:01AM (#39455457)
We use Gerrit internally and use GitHub as a pseudo-mirror. We allow (and welcome!) community contributions to GitHub via PRs.

Our internal Changelists in Gerrit get synced to GitHub as those PRs you are seeing (the branch names correspond to Gerrit change-ids), and any community PRs get copied to our Gerrit first before going through CI and then being merged and synced with GitHub.

[ Parent | on HN ]