3 ms·
At some point a new build needs to roll out to production. There's always going to be some risk that something goes wrong, so better to test with 2% of the popu
by copecopecope 6y ago
At some point a new build needs to roll out to production. There's always going to be some risk that something goes wrong, so better to test with 2% of the population initially rather than 100%. By then, the build has already gone through integration tests/dog-fooding, so if something goes wrong in the canary phase, it's generally due to some production environment configuration issue.
- toomuchtodo 6y agoNot disagreeing, simply stating users should be aware and get a say (an option would be fine to opt in to early release access), especially if they’re a paying customer.
- copecopecope 6y agoI hear where you're coming from, but from my experience, the canary phase usually lasts less than an hour. And the traffic is usually split randomly, so the same 2% of users aren't at elevated risk for every deployment. I don't know how Slack does it, though.
- deleted 6y ago[deleted]