4 ms·
Interesting ... what's your QA process? Do you have a staging environment where you try stuff out (looking for bugs) before pushing to production?
by trustfundbaby 14y ago
Interesting ... what's your QA process? Do you have a staging environment where you try stuff out (looking for bugs) before pushing to production?
- psadauskas 14y agoWe have a staging environment, but its really only used for really big changes that might need to be experimented with before being deployed. We can also deploy a branch to a single front end to observe how it behaves with a subset of the traffic, and roll it back quickly if needed. Also, most large user-facing features are released as "staff-only" first, so we as GitHub users are able to play around with it for a few days or weeks before enabling it for everyone.
- vrish88 14y agoHow do you guys release features as "staff-only"? Do you have some internal tool that manages that?
- rtomayko 14y agoNo. There's simple conventions for adding feature flags (user.some_feature_enabled?). Features are enabled and disabled by changing the code and deploying. This works because deploying new code is fast.
- technoweenie 14y agoWe do use Rollout (https://github.com/jamesgolick/rollout https://github.com/jamesgolick/rollout) once in awhile. Most of the time, we like having the history of flipped feature flags in the Git code though.