-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: support of partial rollouts of patches #783
Comments
Implementing this would allow for customers to test/verify patches before releasing them to their full user base. |
I think what the customer is asking for is just a way to test a patch locally on their device, before going live. So something as simple as:
Which then says at the end:
|
Another way might be:
|
Another proposal from Felix is to just make So the flow would be:
You could imagine having a flag: |
This should be done now 🎉 |
This is related to #110, but #110 was closed after the infrastructure was landed, but before we actually released a fully working feature.
What blocked our release of a fully working feature, was that we realized we had no way to know which devices were/weren't in a specific test group from Google/Apple.
However upon further discussion with customers, simply disabling automatic update behavior e.g. #716 may be sufficient for them to implement this themselves, but making their own call to their servers and then choosing based on the user/device whether to install a patch via package:shorebird_code_push apis.
This bug covers completing the work to make partial rollouts of packages work (via whatever mechanism).
Some customers may also wish to use this for A/B testing (which may imply additional analytics work).
The text was updated successfully, but these errors were encountered: