# Pietro Albini - Shipping a Compiler Every Six Weeks (Highlights)  ## Metadata **Cover**:: https://readwise-assets.s3.amazonaws.com/static/images/article4.6bc1851654a0.png **Source**:: #from/readwise **Zettel**:: #zettel/fleeting **Status**:: #x **Authors**:: [[Pietro Albini]] **Full Title**:: Shipping a Compiler Every Six Weeks **Category**:: #articles #readwise/articles **Category Icon**:: 📰 **URL**:: [www.pietroalbini.org](https://www.pietroalbini.org/blog/shipping-a-compiler-every-six-weeks/) **Host**:: [[www.pietroalbini.org]] **Highlighted**:: [[2021-02-21]] **Created**:: [[2022-09-26]] ## Highlights - we have no pres­sure to ship things. - how can we actu­ally prevent regres­sions from reach­ing the stable chan­nel? - the first answer is the compil­er’s test suite - Why don’t we test our users’ code ourselves? This is an idea that seems really bad and seems to waste a lot of money but it actu­ally works and it’s Crater. - For each project we run cargo test two times, once with stable and one with beta, and if cargo test runs on stable but fails on beta then that’s a regres­sion, and we get a nice colour­ful report where we can inspect.