One thing I forgot to mention explicitly but that is worth following up on: we should generally be striving to get rid of code that is enabled/disabled based on the value of MOZ_UPDATE_CHANNEL. If you are responsible for any such code, please file bugs to switch them to using these build defines, wherever possible (and where not possible, file a bug to investigate adding a define that better addresses the specific use case). Bug 875342 is one such example.
Gavin On Thu, May 16, 2013 at 5:04 PM, Gavin Sharp <ga...@gavinsharp.com> wrote: > Bug 853071 landed in the Firefox 23 cycle, adding some defines that make it > possible to control when in the release cycle code is built. > > I've described the various defines here: > > https://wiki.mozilla.org/Platform/Channel-specific_build_defines > > To recap: > > NIGHTLY_BUILD is defined when milestone.txt contains "a1", i.e. for > mozilla-central builds. > > RELEASE_BUILD is defined when milestone.txt does not contain "a", i.e. for > builds off of mozilla-beta or mozilla-release. > > EARLY_BETA_OR_EARLIER is defined depending on the corresponding value in > build/defines.sh. This file is managed manually by the release management > team, with the variable being cleared once we're past the "early beta" point > in the release cycle. > > All of these defines are both AC_DEFINE (preprocessors) and AC_SUBSTed > (autoconf/makefiles). > > (RELEASE_BUILD existed previously, but was only defined in pref files. It's > now "global".) > > Gavin > > _______________________________________________ > firefox-dev mailing list > firefox-...@mozilla.org > https://mail.mozilla.org/listinfo/firefox-dev > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
