Progressive rollouts for release features
The latest Firefox release (141) on Android introduced a couple of new features marked as "progressive rollout", e.g. the ability to protect private tabs via PIN, while t… (మరింత చదవండి)
The latest Firefox release (141) on Android introduced a couple of new features marked as "progressive rollout", e.g. the ability to protect private tabs via PIN, while the release also brought regular updates, e.g. security fixes.
Does someone know how a progressive rollout of such a feature works technically for the userbase? How can a release be rolled out, but some of its features be kept back while other changes apply to all?
For example, the ability to set a PIN for private tabs is a local user preference configuration. The user may or may not have a user sync profile. How is it possible to rollout the feature progressively on the same release channel? Or does the progressive rollout imply the first group of users receive the feature with consecutive minor releases, e.g. release 141.1, the next group with 141.2, etc?