|
|
|
|
|
by arachnid92
224 days ago
|
|
The way we do it where I work (large company in the cloud/cybersecurity/cdn space): - Chains of manageable, self-contained PRs each implementing a limited scope of functionality. “Manageable” in this context means at most a handful of commits, and probably no more than a few hundred lines of code (probably less than a hundred tbh). - The main branch holds the latest version of the code, but that doesn’t mean it’s deployed to production as-is. Releases are regularly cut from stable points of this branch. - The full “product” or feature is disabled by a false-by-default flag until it’s ready for production. - Enablement in production is performed in small batches, rolling back to disabled if anything breaks. |
|