canmove, Confirmed users
6,441
edits
No edit summary |
|||
Line 14: | Line 14: | ||
=== Nightly Updates === | === Nightly Updates === | ||
When a branch that receives nightly updates is set-up, a rule will be added that maps all users on its nightly channel to a release identified by $product-$channel (Eg, Firefox-nightly)< | When a branch that receives nightly updates is set-up, a rule will be added that maps all users on its nightly channel to a release identified by $product-$channel-latest (Eg, Firefox-nightly)<sup>[[#note1|1]]</sup>. This is a one time set-up and requires no additional maintenance down the road. | ||
When a new nightly build is ready to be published, the build machine will add it to the AUS database in two places: the $product-$channel-latest release, as well as a $product-$channel-$buildid release. Once the -latest release has been updated the new updates are live. | |||
== Web Administration == | == Web Administration == | ||
Line 130: | Line 132: | ||
| Delete the rule | | Delete the rule | ||
|} | |} | ||
== Footnotes == | |||
<span id="note1">$product-$channel-latest only works in a world where no channel names overlap, which we should be in once 1.9.2 is dead. Doing it this way ensures that we nightly updates work after version bumps happen *and* we don't need to maintain a branch name <-> version mapping a la existing AUS.</span> |