Closed Bug 1052531 Opened 11 years ago Closed 11 years ago

build flags for beta version?

Categories

(Firefox Graveyard :: SocialAPI, defect)

Product:
Firefox Graveyard
Component:
SocialAPI
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: mixedpuppy, Unassigned)

Details

In bug 8466509 I am using RELEASE_BUILD wrongly assuming it meant actual release, not release+beta. We want to run stuff on beta, and I'd like a way to ensure I pref some stuff of for release to avoid any potential of forgetting to patch the pref for release. I think this would be generally useful to help pref off until we want to actually release. One option suggested by @jaws was a new flag. Only other option I can think of is a bug with a ready patch tracking for release.
Of course, the third option is to not test things in Beta. I know we want Beta to be as close to what Release will be as possible, so introducing this flag may complicate the expectations/testing.
We have EARLY_BETA_OR_EARLIER. As jaws says, we generally shouldn't be using late betas as a test bed. Bug 8466509 is a typo - which bug did you mean?
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
(In reply to :Gavin Sharp [email: gavin@gavinsharp.com] from comment #2) > We have EARLY_BETA_OR_EARLIER. As jaws says, we generally shouldn't be using > late betas as a test bed. For the share panel activation, Madhava wanted to get telemetry data on the beta channel before it goes to release. > Bug 8466509 is a typo - which bug did you mean? heh...wonder how I did that. bug 1014332
EARLY_BETA_OR_EARLIER works fine for that.
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.