Mozilla Automation TeamLudovic Hirlimann3 min readintro
20+ years of running "alpha quality" browser as my main web browser
Summary
The author has been using Firefox Nightly for about 20 years, mixing personal and work usage while regularly filing crash reports. He argues that nightly builds can be stable enough for daily work and that crowd‑testing and crash telemetry are valuable for Mozilla’s stability team.
- Nightly Firefox can remain usable for years; occasional crashes are mitigated by regular crash reporting.
- Running separate channels (nightly for personal, release for work) isolates risk while keeping access to new features.
- Crowd‑testing fills gaps that a QA team cannot cover across all hardware‑software combos.
- Submitting crash reports directly influences Mozilla’s stability priorities.
Browser engineers and QA professionals should see how sustained nightly usage and systematic crash reporting can improve stability and inform development priorities.
5/10



