> The long and short of it is that whatever branching model you decide to > use, its success depends on discipline and documentation more than > anything else (as well as fitting the tool's (mis)features, of course). > Whether or not cascading branches work for you really depends on whether > they fit your development and release management methods.
All of that is true of course, but one last word from me about cascade: https://issues.apache.org/jira/browse/SVN-3495 - was the facilitator (in an airline doing concurrent development of consecutive releases) for a permanent flip from cascade to canonical trunk based development (with build+boot+runtime toggles/flags and branch by abstraction). The airline went multi-repo in Git some years later, and does the GitHub-flow model (not GitFlow) but it is still the same ... *except for the loss of atomic commits.* - Paul
