We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

nightly <reloaded/>

Formal Metadata

Title
nightly <reloaded/>
Alternative Title
Rebooting Firefox Nightly: A community building project around the Firefox Nightly Channel
Title of Series
Number of Parts
611
Author
License
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language
Production Year2017

Content Metadata

Subject Area
Genre
Abstract
A community building project around the Firefox Nightly Channel Every day, we compile the code for Firefox on our master branch, mozilla-central, and generate builds without the Firefox branding, those are calledFirefox Nightly build. Until recently, those builds were barely mentionned orpromoted on mozilla.org, localized versions existed but were only known to thelocalizers themselves, the download page was on a separate domain and hadn'tbeen redesigned since 2011. As a result, we have very few Firefox Nightly users. What would be the impact for Mozilla if Firefox Nightly became a first-classcitizen among Firefox channels? How about getting back more technical users onthis channel reporting bugs as they get introduced into our codebase insteadof weeks or months later? Could we ship faster and better quality software ifwe had an army of Nightly testers reporting regressions and giving theirfeedback on a daily basis? How about engaging our existing community of power-users directly into the production process for Firefox as a long termparticipation project? This talk is a recap of what the release management team has been working onin the last 8 months to turn the nightly channel in a more useful toolleveraging our existing community to ship a better Firefox and what we expectto do in 2017 around the nightly channel to serve our QA needs.