Platform/Channel-specific build defines: Difference between revisions

← Older edit

Platform/Channel-specific build defines (view source)

Revision as of 16:12, 13 May 2020

467 bytes added , 13 May 2020

m

We set the EARLY_BETA_OR_EARLIER after beta 5 now

Pascalc

Confirmed users

1,255

edits

@@ Line 17: / Line 17: @@
 ==EARLY_BETA_OR_EARLIER==
-This 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. It is usually done after beta 4, i.e. shipping in Beta 5.
+This 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. It is usually done before the final beta build of week 2 ships during the cycle (typically beta 6).
 This define was added in the Firefox 23 cycle.
-* '''Note:''' use of this flag requires explicit approval from [[Release Management]].
 * '''Note:''' this flag is currently not defined for the JS build ({{bug|879836}})
+==Usage==
+The aforementioned variables are mutually exclusive.
+So for instance, if you wanted to enable a feature on Nightly and Dev, you'd have to use <code>NIGHTLY_BUILD || MOZ_DEV_EDITION</code>. Features using <code>EARLY_BETA_OR_EARLIER</code> will show up in Dev, but not consistently so (as with Beta), so <code>EARLY_BETA_OR_EARLIER || MOZ_DEV_EDITION</code> might make sense, depending.
+(Also note there is intentionally no single variable covering Beta, as late Beta becomes/is Release.)
+==Other==
 You may also be interested in [[Platform/Platform-specific_build_defines]]
 [[Category: Release Management]]