4 ms·
It’s managed through Git workflow. At one place we had three branches: master, alpha and release. Master was in-progress features. By the time alpha was cut yo
by jdavis703 5y ago
It’s managed through Git workflow. At one place we had three branches: master, alpha and release.
Master was in-progress features. By the time alpha was cut you were expected to be code complete because that was also the end of the sprint.
Alpha then went to staging servers. Bug fixes would land in master and be cherry-picked in to alpha. Eventually alpha gets promoted to release.
Emergency fixes are cherry picked directly to release.
It’s clunky and stressful, but that’s we did it at one startup I worked about 10 years ago. Everywhere uses flags.
- mkdirp 5y agoThis is mad. So much overhead for little to nothing. Even if you don't use feature flags, you should always be merging complete code. Master should be your release, and you should be deploying often. The small your release, the quicker you catch issues, and the easier it is to understand where those issues lie.