I spent twelve years as a production engineer at a Montreal colocation firm, mostly wrestling with x86_64 firmware bugs and the occasional kernel panic. In November 2016, a routine package upgrade bricked our storage cluster because the new I/O scheduler ignored the quirks of our SAS controller. The fix shipped in an out-of-band patch from a maintainer in Vancouver who kept the driver alive as a side project between consulting gigs. That commit didn’t just save our nodes — it changed how I saw the relationship between infrastructure and the people who build it. LinuxCanada started in 2017 as a way to keep tracking those connections, one commit at a time.
Our mission is simple: track the kernel and package updates that originate from, or significantly affect, Canadian open-source contributor projects. Not just merge commits — we document release notes, CVE impact, and the downstream packaging decisions that matter when you run these components in production. Every entry is verified against the upstream tree and distro bug trackers, and we link back to the original submission so you can read the rationale before you patch. We don’t aggregate press releases; we trace the technical trail from mailing list post to stable release, with the specific hardware and workload context that sysadmins need. That commitment to provenance means you’ll find the same driver here that saved our storage cluster, plus the twenty follow-up fixes that made it reliable.
If you maintain a project from Canadian time zones, or if you’re responsible for a fleet that depends on one, we want to hear your upgrade war stories. Corrections and edge cases are especially welcome — a disputed timestamp or a missing dependency note helps us sharpen the record for everyone. Send tips through our Contact Us page; we read every message and will update the tracker with attribution and a credit. LinuxCanada is built by someone who’s been woken up by a bad commit, and it stays useful only if you tell us where the trail goes cold.