Closed Bug 1643392 Opened 5 years ago Closed 4 years ago

On macOS, Firefox Beta's Bundle ID is the same as FireFox Stable's

Categories

(Release Engineering :: General, defect)

x86_64
macOS
defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: me, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:79.0) Gecko/20100101 Firefox/79.0
Firefox for Android

Steps to reproduce:

On macOS, Firefox Beta's bundle ID is org.mozilla.firefox, which is shared with the stable release channel. This differs from, for instance, Firefox Nightly, which has the bundle ID org.mozilla.nightly.

Actual results:

Since my employer manages updates on macOS for stable Firefox releases using the bundle ID, Firefox Beta's automatic updates are also disabled. I've confirmed that this is an unintentional side effect of their management policy.

Expected results:

I'd like to use unstable features (WebRender; etc.) but without updating as often as I do with Firefox Nightly. Firefox Beta is a good compromise in update frequency compared to Nightly. My day-to-day usage of Firefox would be greatly improved if Firefox Beta had different bundle ID along the lines of org.mozilla.beta.

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Graphics: WebRender
Product: Firefox → Core
Component: Graphics: WebRender → General
OS: Unspecified → macOS
Product: Core → Firefox Build System
Hardware: Unspecified → x86_64
See Also: → 1406662

Hi release folks! Is this request something that can feasibly be implemented? What consequences are there to updating a macOS bundle ID? Before thinking about how we might implement this on the build side I want to confirm that this is something that we should, or can, practically do.

Product: Firefox Build System → Release Engineering
QA Contact: catlee
Version: 78 Branch → unspecified

I believe this is as designed, so we can update beta users to RC releases.

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.