It’s another monthly burst of news about bors-ng, because if your primary development branch has failing tests, you don’t have a code problem; you have a process problem.
In the last month, we landed 13 PRs in the bors-ng repository.
Get this newsletter via email
This newsletter is getting sent out via MailChimp, now, too. Just put in your email, and on the third day of every month, you’ll get an email with the same stuff as this post.
- notriddle fixed a bug that caused delegation to crash
- notriddle fixed a bug that caused actually-good reviews to be rejected
- notriddle raised some timeouts that were being hit on big repositories
- notriddle fixed a crash when the same pull request is delegated twice
No new contributors this month 😥
Want to see your name in this newsletter? Look at bors starters, a curated list of issues that are good for new contributors!
Who’s using bors?
CockroachDB is a distributed relational database that speaks the PostgreSQL client-server protocol as a drop-in replacement for existing apps.
It has a sharding and replication algorithm built-in, which maintains high availability and consistency in many common failure scenarios. A CockroachDB cluster will maintain consistency by going down if a majority of nodes can’t reach each other (it is a CP distributed data store). It supports, but doesn’t require, you to define availability regions and replication rules.
Cockroach Labs runs a self-hosted instance of bors-ng and TeamCity called “craig” on Google Cloud. They’ve been great help getting the self-host documentation and Docker Hub working well.
Got any suggestions for next month? Post a comment on the September pull request.