Lukas Blakk schrieb:
* Releng automation to switch/edit mozconfigs for earlier betas to check for this flag
I think it would be good if we wouldn't have to rely on releng there, as this again introduces the factor of someone possibly forgetting to do this. Ideally this should be fully automated, or at least depend on something obvious that many eyes can check easily (which something buried in several platform-dependent mozconfigs probably isn't).
Also, I think that people building themselves from the beta repo (or, say, Linux distros), should ideally get the same feature set that our builds do, so it would be good if this flag was triggered by something in the actual source. Maybe we should have a simple file in the source trigger this flag (just like the simple files with versions trigger RELEASE_BUILD) and have an automated script that checks daily how long it has been since the last uplift and sends an email warning to relman or so if the value of that file doesn't match our expectation. Having someone do a minimal checkin there around the middle of every beta cycle doesn't sound too bad, and the warning would ensure that happens. Also, if we'd miss it, we notice that a beta that should not have "early beta" functionality actually does, and the checkin can be done and will persist for the rest of this train. It would be even better if we could completely automatically detect if some state of the source is "early beta" or not, but I don't know how that would be possible from the source alone. (The current date itself isn't good as a distinction as someone could go back and try to bisect commits and re-build to find a regression, just to be confused, as the regression might have been caused or fixed by turning that flag - another reason why it should be in the source repo.)
Robert Kaiser _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
