3 ms·
I use: 1. Master should be always deployable: 2. All features are a separate branch BUT, when merged into master they should also have a config for ON/OFF. Th
by rawoke083600 7y ago
I use:
1. Master should be always deployable:
2. All features are a separate branch BUT, when merged into master they should also have a config for ON/OFF. This has the benefit of quickly switching between old and new behaviour(feature) as well as forcing a "module-based-architecture" for the code.
- borplk 7y agoOne problem with #2 is many types of changes are impossible to toggle on/off (I mean "change to codebase" not "product feature").
- rawoke083600 7y agoTrue, #2 is not always feasible, but lol the dev can damn well try :P