3 ms·
I immediately spot one huge issue with this > The production branch is essentially a monolith – a single long-running production release It assumes that only
by alkonaut 6y ago
I immediately spot one huge issue with this
> The production branch is essentially a monolith – a single long-running production release
It assumes that only one version is deployed at a time, so you can't really service version1.0 after you shipped version2.0.
Having multiple independent maintenance branches for production is critical for any branch pattern that should apply to both web software (normally single deployed version) and e.g. Desktop (normally multiple deployed versions).
Th