2 ms·
Because then it stops being "trunk-based development" but unholy hybrid of few approaches. There is no notion of multiple stable releases getting patches in tr
by ilyt 4y ago
Because then it stops being "trunk-based development" but unholy hybrid of few approaches.
There is no notion of multiple stable releases getting patches in trunk based development.
- jeffbee 4y agoWhy do you think this? There is nothing about trunk-based development that rules out having several live release branches. Google is the poster boy for TBD in the article, and in their main monorepo there are always numerous live release branches but it is still trunk-based. Fixes go into main and are down-integrated to the releases.
- twic 4y agoNonsense. Multiple release branches are a perfectly normal part of TBD. See: https://trunkbaseddevelopment.com/branch-for-release/ https://trunkbaseddevelopment.com/branch-for-release/ Note in particular "the CI pipeline that guards the trunk is going to be duplicated to guard active release branches too" - branches plural.